Allow hashable-1.5 #1071
Merged
Allow hashable-1.5 #1071
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
phadej
force-pushed
the
hashable-1.5
branch
2 times, most recently
from
f4cad08
to
95641a7
Compare
RyanGlScott
reviewed
Jul 5, 2024
|
I've added a corresponding Hackage revision. |
|
Thanks, I'll try to act ASAP after |
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 took a liberty to add
allow-newers tocabal.project. Other packages intheseandstrictrepositories themselves depend onlens, so having a revisedlens(andsemigroupoids) would help updating them in one go. I'll make another PR to remove theseallow-newerfields once the updates are done.EDIT:
lensdoesn't useHashable1norHashable2so it's not affected by changes inhashable-1.5.