-
Notifications
You must be signed in to change notification settings - Fork 22
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
Empty String Rules Fail to Match #108
Comments
since the behavior is varying across those similar grammars, this seems like a bug to me. I have a hunch! so thanks for the great reproduction steps, and I will start investigating 🕵️ |
@Axiomatic-Mind I just merged the PR that addresses this, the release will be publised to crates soon. Thanks for raising the issue! |
okay version 0.4.2 published to crates.io! |
Thanks for fixing this! |
This was referenced Dec 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I match a grammar such as
against
foo:bar
, it works. When I match a grammar such asagainst
foo:
, it works. However, when I matchagainst
foo:
, it doesn't work.Replicable using this code:
Why isn't a parse tree like this being generated?
Is this intentional/explicable behavior, or a bug? Thanks!
The text was updated successfully, but these errors were encountered: