Move Text.Megaparsec.State into exposed-modules
#549
Merged
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
|
Thanks! |
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.
#539 exported
initialStateandinitialPosState, and the CHANGELOG for 9.6.0 indicated that these are now available for use. Unfortunately, they are not, since they were exported fromText.Megaparsec.State, which itself is not exported from the package. This PR simply movesText.Megaparsec.Statefromother-modulestoexported-modulesto allowinitialStateandinitialPosStateto be used as advertised.If another solution is considered more desirable (e.g. re-exporting
initialStateandinitialPosStatefrom some other module) I'd be happy to modify the PR or open a new one.