Add a combinator then_or_not to optionally run a parser after another
#733
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #630, which first mentioned something like this.
This can be used in syntaxes like Rust's let statement, which has an optional type notation:
.then(...).or_not()doesn't work well in such cases, because when there's a parse error in the type,or_notwould just suppress it and returnNone, leaving the following parsers confusing, or even worse, mistakenly starting parsing from the wrong position. In this particular example, when the type has an error, the parser may complain something likeexpected '=', got ':', rather than pointing out the error in the type.With
then_or_not, Rust's let statement can roughly be parsed with:And this would correctly report the errors in
rust_typeandexpr.