-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#2326, GHC 8.4 compatibility #2796
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
It would be great if you could also add a |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
CI is failing due to hlint. |
Added a stack84.yaml, so now you can successfully run:
Also fixed the HLint errors and a warning. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks for the updates! HLint is sadly, still unhappy. I recommend that you run the |
Fixed HLint (I didn't have it installed on this machine...) |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks like a flake. |
* digital-asset#2326, GHC 8.4 compatibility * Fix up CI * Add a Shake lower bound * Upgrade to a hie-bios which is GHC 8.4 compatible * Add a GHC 8.4 stack * Fix HLint again
Fixed it up. After that, hie-core built with GHC 8.4 can compile hie-core.
I also added a message about which GHC you used on startup, since that seems to be a common mistake people are making.