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
optionalIndent — for things that are optionally indented
sameLevel — for things that should not be indented
Another option is to automatically insert { and } based on indentation in the tokeniser, but I'm not sure how ergonomic that would be to use.
Yet another option could be to have a more hierarchical parser, where you are explicit about parsing subtrees. Basically, each parser would take a rose-tree as input so there is no risk of confusion between indented subtrees and unindented nodes.
The text was updated successfully, but these errors were encountered:
I'm thinking we could use these combinators:
indented
— for things with higher indentationoptionalIndent
— for things that are optionally indentedsameLevel
— for things that should not be indentedAnother option is to automatically insert
{
and}
based on indentation in the tokeniser, but I'm not sure how ergonomic that would be to use.Yet another option could be to have a more hierarchical parser, where you are explicit about parsing subtrees. Basically, each parser would take a rose-tree as input so there is no risk of confusion between indented subtrees and unindented nodes.
The text was updated successfully, but these errors were encountered: