CI: GitHub: Nix: make GHC 8.8 nonstrict #782
Merged
Conversation
This file contains hidden or 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
For quite some time 8.8 strict build fails:
```
src/Nix/Expr/Types.hs:179:10: error: [-Wmissing-methods, -Werror=missing-methods]
• No explicit implementation for
‘liftTyped’
• In the instance declaration for ‘Lift (Fix NExprF)’
|
179 | instance Lift (Fix NExprF) where
| ^^^^^^^^^^^^^^^^^
```
`nomissing-methods` seems like a bad path in this case and module.
I tried to adddess the issue and so far not constructed the implementation.
Too bad that the issue creaped-up backwards. Strict builds worked until this one
cropped-in.
So lowering the CI strictness until this gets resolved.
This was referenced Dec 29, 2020
Merged
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.
For quite some time 8.8 strict build fails:
nomissing-methodsseems like a bad path in this case and module.I am quite new with Template Haskell, I tried to address the issue and so far not constructed the implementation. I think more TH knowledge is needed.
Too bad that the issue creeped-up backwards. Strict builds worked until this one popped-up.
So lowering the CI strictness until this gets resolved.