-
Notifications
You must be signed in to change notification settings - Fork 152
Support for ghc-9.0.1 #378
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@jaspervdj, is there any news on this? It would be appreciated if we can hear some plans or difficulties. |
Even better if we could get 9.2.1 support as well! |
I started a branch for the jump to 9.2. There's been a fair amount of changes that impact how we use the API. Overall they're improvements so they'll give me an opportunity to clean up some stuff. I expect to finish this in a couple of weeks. |
Currently, all but two of the larger steps ( |
Is there a branch one compile to have stylish-haskell work with GHC 9.2.1/2? |
@Mikolaj You can try the |
Thank you for the hint. I've just tried it, with GHC 9.2.2 and got:
Not 100% sure it's stylish-haskell's fault. I haven't tried with GHC 9.2.1. |
Thank you! But something weird happened --- newest commits are now from 2013. |
And on branch ghc-9.2 with GHC 9.2.2 I'm still having
|
And indeed
fails with
|
|
GHC 9.2.2 |
@Mikolaj I've published a metadata revision to hackage (and the |
@jaspervdj: but the error #378 (comment) is not a dep version problem, right? |
@Mikolaj correct, but I think the error there is the result of using |
Makes sense, but sadly I'm getting
|
And the same on a branch called "main", after pulling. |
@Mikolaj I've uploaded a new version that picks dependencies based on what hlint does. Would you mind trying again? I verified this works on a blank ubuntu image with ghc-9.2.2. |
It works. \o/ |
The text was updated successfully, but these errors were encountered: