-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Possible values verification doesn't work #287
Labels
Milestone
Comments
Thanks for taking the time to file this! We'll post back here with updates and should have this fixed quickly. |
kbknapp
added
C-bug
Category: Updating dependencies
P1: urgent
A-parsing
Area: Parser's logic and needs it changed somehow.
labels
Sep 30, 2015
Offending lines are most likely here I'll fix in the morning if someone hasn't beaten me to it by then 😉 |
kbknapp
added a commit
that referenced
this issue
Sep 30, 2015
homu
added a commit
that referenced
this issue
Sep 30, 2015
fix(Possible Values): possible value validation is restored Closes #287
👍 |
v1.4.3 is out on crates.io which fixes this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can be reproduced using example 11_only_specific_values.
actual
If invoked with any value (other than
fast
andslow
) it triggers panic:thread '<main>' panicked at 'internal error: entered unreachable code', src/main.rs:32
expected
Some error message, graceful exit and usage info printed.
The text was updated successfully, but these errors were encountered: