[AST Builder]

AST Builder

The builder is the semantic boundary between ANTLR’s concrete parse tree and PYNE’s ASDL abstract tree.

Abstract

src/pynescript/ast/builder.py defines three cooperating mixins:

1. PinescriptASTLocator — maps ParserRuleContext.start/stop tokens to lineno / col_offset / end_*.
2. PinescriptCommentParser — classifies //… text into annotation kinds (@=S, @0F, #, plain //, …).
3. PinescriptASTBuilder — subclasses generated PinescriptParserVisitor, implements visit_* for every meaningful rule, returns ASDL nodes.

helper._parse constructs a builder, runs builder.visit(rule_context), then (in exec mode) uses StatementCollector + comment tokens to attach annotations. The builder itself does not walk the default token channel for comments; that is a post-pass.

Conceptual model

Interface surface

You rarely instantiate the builder directly; parse() does. For tools that already hold a parse tree:

from pynescript.ast.builder import PinescriptASTBuilder
from pynescript.ast.grammar.antlr4.parser import PinescriptParser
# ... construct parser, parse to ctx ...
node = PinescriptASTBuilder().visit(ctx)

Locator API

End column calculation accounts for embedded newlines in the stop token text.

Comment kinds

_parseComment returns (kind, parts):

helper._add_annotations filters by suffix when attaching to nodes.

Store context

_set_store_ctx walks assignment targets (Name, nested Tuple) and sets ctx = Store() so load/store distinction is available to later passes (Python-ast style).

Representative visit methods

Expression climbing follows the grammar’s layered rules (conditional → disjunction → conjunction → equality → inequality → additive → multiplicative → unary → primary).

Internals

Path

• Implementation: src/pynescript/ast/builder.py
• Visitor base: src/pynescript/ast/grammar/antlr4/visitor.py → generated PinescriptParserVisitor
• Node types: src/pynescript/ast/node.py
• Annotation pairing: src/pynescript/ast/collector.py + helper._add_annotations

Statement list flattening

visitStatements flattens each statement visitor’s result: some rules return a list (simple multi-statement lines joined by commas), so the body is always a flat list[stmt].

Export flag

When EXPORT is present on library declarations or compound name initialization, the builder sets export = 1 on the corresponding node (integer flag per ASDL int?).

Field / enum members

Field definitions become Assign-like statements inside TypeDef.body (with optional VarIp mode). Enum members become assignment-shaped stmts under EnumDef.body. The unparser special-cases method members of types when pretty-printing.

Invariants

1. Every constructed stmt/expr that has a source span should receive _setLocations so LSP diagnostics and get_source_segment work.
2. Visitor method names must track generated rule names. Renaming a parser rule without updating the builder is a silent generic_visit fallback (wrong or empty trees).
3. Do not edit builder.py.bak. Live builder is builder.py only (stale backups are forbidden under project policy).
4. Grammar and builder co-evolve. A resource-only grammar change that adds rules is incomplete until visit_* exists.

Worked examples

What x = close + 1 becomes

Rough structure after build:

Assign(
  target=Name(id="x", ctx=Store()),
  value=BinOp(
    left=Name(id="close", ctx=Load()),
    op=Add(),
    right=Constant(value=1),
  ),
)

Export const initialization

Grammar: EXPORT? variable_declaration EQUAL structure_expression

Builder sets assign.export = 1 when ctx.EXPORT() is present — required for library export of typed constants.

Debugging a missing visitor

from pynescript.ast.helper import parse, dump
print(dump(parse(your_snippet), indent=2))

If a subtree is None or a raw unexpected type, find the rule in PinescriptParser.g4 and the matching visitRule_name in builder.py.

Failure modes

See also

• Grammar (ANTLR4)
• ASDL schema
• Helper API
• Error model