Added the Text.Parser.Input module #80
Closed
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
|
Since the newly-published construct needs these classes, I've added them there for the time being. You can see how they're used. I'd still prefer them here in parsers. |
This reverts commit 6bfa1a1.
|
Never mind then. I have published a new package input-parsers instead. |
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.
I wonder if you'd be open to adding another module to the library, with a couple of classes for efficient parsing of arbitrary monoidal inputs? I've used variations of these classes in grammatical-parsers, but that package would be a heavy dependency and I feel this would be a better home for them. If not, I'll probably resort to creating yet another small package.
I'd be happy to add more instances and tests if the module is acceptable.