Avoid hlint parse error on "pattern", rerun hlint --default. #46
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
keelerm84
approved these changes
Nov 2, 2022
|
Thanks again @philderbeast I appreciate all these contributions. Do you plan on providing more PRs over the next couple of days or would you rather I cut a release with the current work first? |
|
@keelerm84 I'd like a release with the cabal file addition (#44) right away if you can do that. |
Closed
|
Sounds good. I'm going to work on cutting a release for you today then. :D |
Merged
|
Hey @philderbeast sorry for the delay. There were a few things conspiring together to undermine my last comment. 😆 But I did finally get the 3.0.3 release out so you should be good to go. Thanks for your patience! |
|
Thanks for making a release @keelerm84. |
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.
HLint enables extensions but for the Operators module this is a problem for "pattern". I chose to disable pattern synonyms for this module but we could have renamed the pattern binding instead. With the parse error avoided, hlint finds more suggestions for us.