Skip to content

Confusing documentation related to src attribute / field #6

@pjljvandelaar

Description

@pjljvandelaar

When reading the documentation

there is a node in the tree. Also every node has a `src` attribute to point at the exact location in the source file
where every node originated.
* You can use handy pattern matching primitives like constructor matching, list matching and deep matching for fast analysis.
* `src` and `decl` fields on AST nodes correspond to the M3 Core model's `declarations` and `uses` relations, and others. Combining
AST analysis with lookups in an M3 core model is usually very handy.

I got confused in multiple ways.

  1. Does the src field correspond to declarations or uses (respectively is missing)?
    And how should I interpret "and others"? Are there additional relations in src? If so, which?

  2. Every AST node has a src attribute to point at the exact location in the source file where every node originated
    AND
    src field on AST correspond to a relation in the M3 Core model.
    Aren't attribute and field synonyms?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions