forked from antlr/antlr4
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement eager pruning of shadowed configs #1
Comments
ghost
assigned sharwell
Feb 13, 2012
sharwell
pushed a commit
that referenced
this issue
Jun 7, 2016
Use File.pathSeparator instead of ":" to support testing on Windows
sharwell
pushed a commit
that referenced
this issue
Jul 18, 2017
Dotnetcore build target with full runtime-testsuite and travis
sharwell
pushed a commit
that referenced
this issue
Dec 23, 2018
Make C# NuGet package name more visible and add link to the package
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In local prediction, a config is shadowed if a higher-priority configuration (according to conflict resolution rules) consumes a superset of its potential inputs. Shadowing occurs in at least the following cases:
(1, 1, [3])
accepts a superset of the inputs of(1, 1, [3 4])
since the invoking state 4 will be in the global follow of state 3.(1, 1, [])
is ambiguous with the configuration(1, 2, [])
, but the former will always be chosen according to min-alts conflict resolution policy.(1, 1, [])
is ambiguous with the configuration(1, 1, [], {1:0}?)
. The predicated config is shadowed by a containing unpredicated config. Note: pruning predicated configs is only valid if the rules for predicate resolution are changed from the "first true predicate" policy to a "minimum valid alt" policy.The text was updated successfully, but these errors were encountered: