Add Parser.orElse() and Parser.orElseEither() #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I am closing this. Mixed github accounts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds two new ways of combining two parsers.
Parser.orElse(other)This function combines two parsers by trying the first one and if it fails trying the other. This function allows the combination of individual parsers for each member of a sealed hierarchy, thus producing a parser for a sum type.
Parser.orElseEither(other)This is combines two parsers like
Parser.orElse()but contrary to theorElse()case the two parser can produce unrelated outputs. Effectively, allows the combination of an two unrelated parsers (outcome wise) with an OR relationship.