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.
This PR introduces a
fail
parser that works as the inverse of thesuccess
parser. It always fails regardless of what input was passed to it. This complements thesuccess
parser and allows specifying default cases to return an error instead.I have come across one use case as part of my precedence parser #1362. It requires three parser for prefix, postfix and binary operators respectively. But some languages might not have any prefix or postfix operators so the respective parser should just fail.
Compared to a workaround like
verify(tag(""), |_: &str| false)
,fail
is easier to read and makes the intent more clear when a parser is required (e.g. as part of a parameter) but should just fail because its not needed in the context.