-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
parser.y: Ambiguous grammar #73
Comments
@shenli PTAL. |
coocood
added a commit
that referenced
this issue
Sep 9, 2015
Resolved all the reduce/reduce conflicts except for 1 Fixes issue #73
resolved by final PR #122 |
YuJuncen
pushed a commit
to YuJuncen/tidb
that referenced
this issue
Apr 23, 2021
* test restore backup after changing its path Signed-off-by: Neil Shen <[email protected]> * restore: override backupmeta path by storage path Signed-off-by: Neil Shen <[email protected]>
xhebox
pushed a commit
to xhebox/tidb
that referenced
this issue
Sep 28, 2021
xhebox
pushed a commit
to xhebox/tidb
that referenced
this issue
Oct 8, 2021
ti-chi-bot
pushed a commit
that referenced
this issue
Oct 9, 2021
Defined2014
added a commit
to Defined2014/tidb
that referenced
this issue
Apr 28, 2022
iosmanthus
pushed a commit
to iosmanthus/tidb
that referenced
this issue
Oct 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that parser.y has several shift/reduce and reduce/reduce conflicts.
S/R conflicts are sometimes expected and/or acceptable, but I don't think this applies in this case. R/R conflicts, on the other hand, are almost never okay.
The current state of the grammar with all of the conflicts means that there are valid sentences, part of the intended-to-parse language, which will parse incorrectly or not at all because the grammar is ambiguous and does not reflect the proper language.
I suggest to get rid of all conflicts in
parser.y
and, above that, perhaps use the-cr
goyacc flag to verify reducibility of all grammar productions.The text was updated successfully, but these errors were encountered: