upgrade ghc-check to fix #3002 #3034
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
|
This should close #3002 |
|
ghc-check 0.5.0.8 is now in Hackage including this fix |
|
Ah, yes, I've upgraded |
pepeiborra
approved these changes
Aug 18, 2022
sloorush
pushed a commit
to sloorush/haskell-language-server
that referenced
this pull request
Sep 12, 2022
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've made some changes in my fork of
ghc-check: kokobd/ghc-check@3522cc2. It does solve the problem for the specific environment mentioned in #3002. But I haven't succeeded constructing a smaller reproducing environment. I'm going to check the CI results here, to see if it breaks something.