-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Surprising whitespace handling #305
Comments
Could you tur these checks into a |
Sure, I was just not sure that the behavior I expect it the intended one. |
A unit test will precisely state the intended outcome. |
dnicolodi
added a commit
to dnicolodi/tatsu
that referenced
this issue
Aug 27, 2023
See #306. |
apalala
pushed a commit
that referenced
this issue
Aug 29, 2023
apalala
added a commit
that referenced
this issue
Oct 13, 2023
fixes #305 * [test] Add test demonstrating expected white space skipping behavior (#306) * [test] add unit test on advancing over whitespace * [parsing] eat whitespace before memoizing * [readme] update statement about Python version requirements --------- Co-authored-by: Daniele Nicolodi <daniele@grinta.net>
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given this example
I find whitespace handling a surprising. The whitespace between
FROM
and the table name is not skipped over before matching thetable
rule. This results in correct parsing but theparseinfo
for thetable
rule. I would have expected whitespace to be skipped before attempting to match thetable
rule.The text was updated successfully, but these errors were encountered: