-
Notifications
You must be signed in to change notification settings - Fork 50
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
post_traverse failure does not fail choice #146
Comments
Hi @foresttoney, can you please expand what you mean, for example, what is the output that you get and what you expected? If you can provide code samples, even better, thanks! |
Yeah - will try to provide some more context. I have a combinator that parses a string in yymmdd format into a Date.
I use the combinator like this:
This has been sufficient to this point because the entire combinator should fail if This is how I imagine it would work:
You can see that using choice here doesn't really matter. |
Let's assume I defined a combinator using post_traverse - something like
parse_date
.My assumption would be that you can define something like:
However, the failure condition defined in parse_date doesn't actually fail the choice combinator - you just end up with the error message as the result of the combinator.
The text was updated successfully, but these errors were encountered: