Expose the main Parsec combinators from the library#57
Open
Expose the main Parsec combinators from the library#57
Conversation
…ld more parsers on top of them.
… suite, since the build seems to nondeterministically fail for lack of it.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Following #56, this is a proposal to expose a couple of main Parsec parsers so that users can compose further combinators on top of them.
My inclination is to be conservative and start small in terms of which parsers we expose.
Note also I exposed the existing parsers under new names, so that
(a) they match the corresponding
parseXfunctions, and(b) they have
...Parserin their names so they're easily identified as Parsec items.