Workaround for type inference regression in GHC 8.1 #274
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
|
Is there reason to believe this won't be fixed before release? I'm generally not a fan of modifying the code base to work around unreleased bugs like this, unless there's some advantage I'm not aware of. |
|
Fair enough. I ran into this while trying to reproduce another bug report with GHC HEAD, that depended on |
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.
resourcetdoesn't build with GHC HEAD (ghc-8.1.20160720), due to https://ghc.haskell.org/trac/ghc/ticket/12427.Here is a workaround.