-
Notifications
You must be signed in to change notification settings - Fork 846
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
Comment regarding comment ambiguity #186
Comments
The example you gave is syntactically incorrect, as there is no ] tag, but I think that the correct parse would be |
Alex, I don't understand what you mean. There is a |
Well, there is a If this answers your question, I believe |
The spec is ambiguous. As I point out in the filing of the issue, it can be read to both allow or disallow comment characters in the keygroup.
|
The specification should be updated to this: |
I've interpreted the spec to allow I think @pnathan is right here. This is an ambiguity. If we fix the wording in the spec, then it needs to be for both table names and key names. Or we could allow |
Fix #186 by disallowing # in keys.
Suppose:
But, consider these definitions - the comment one first:
vs.
and:
This results in two correct parses:
describe.number.
ordescribe.number.#
.While ambiguity is good in poetry, it drives parsers mad.
The text was updated successfully, but these errors were encountered: