-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing names in the grammar #353
Milestone
Comments
OmarTawfik
changed the title
Remove any automatically generated names in grammar
missing names in the grammar
May 3, 2023
OmarTawfik
added a commit
that referenced
this issue
May 24, 2023
OmarTawfik
added a commit
to OmarTawfik-forks/slang
that referenced
this issue
Jun 10, 2023
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 7, 2023
Adds validation to make sure that: - Productions cannot reference itself, except operators. - Required productions cannot be inlined. - Parsers cannot reference inlined scanners. - Scanners can only reference inlined scanners. - Parser names should be unique, except operator definitions, and parsers defined in different versions. - Prevent useless nesting of parsers if they don't change the output. - make sure keywords are always referenced as productions instead of terminals everywhere in grammar, to guarantee that the correct version checks run on them. Closes #353
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unnamed nodes in the grammar don't produce their own
TokenKind
orRuleKind
. And they are absorbed into the parent node. We should go over the grammar, make sure unit tests cover each version, variant, and branch of each production, and check the generated CST shape.The text was updated successfully, but these errors were encountered: