You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the tree sitter node navigation commands, "named" visits too few nodes, while "all of them" visits too many. I'd say we're looking for the behavior that "all" has, except that it shouldn't visit punctuation like , and closing delimiters like ].
(a) Does tree-sitter provide some metadata on the node that we could use to tell that it's "empty", e.g. punctuation or a closing delimiter? If it does, then we could use the "all" behavior while avoiding such "empty" nodes.
(b) Another (less desirable) possibility is to have an exclusion list that skips over these at the symex level.
(c) A third possibility is to do nothing and leave it as "named" nodes, especially if we agree it would be preferable to option (b) above (e.g. would (b) require maintaining separate exclusion lists for different languages?).
Additional context: see this comment and the responses.
The text was updated successfully, but these errors were encountered:
In the tree sitter node navigation commands, "named" visits too few nodes, while "all of them" visits too many. I'd say we're looking for the behavior that "all" has, except that it shouldn't visit punctuation like
,
and closing delimiters like]
.(a) Does tree-sitter provide some metadata on the node that we could use to tell that it's "empty", e.g. punctuation or a closing delimiter? If it does, then we could use the "all" behavior while avoiding such "empty" nodes.
(b) Another (less desirable) possibility is to have an exclusion list that skips over these at the symex level.
(c) A third possibility is to do nothing and leave it as "named" nodes, especially if we agree it would be preferable to option (b) above (e.g. would (b) require maintaining separate exclusion lists for different languages?).
Additional context: see this comment and the responses.
The text was updated successfully, but these errors were encountered: