-
Notifications
You must be signed in to change notification settings - Fork 21
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
ghc 8.10 and ghc-prim bound #65
Comments
😱 |
I know this is being tracked via polysemy-research/polysemy#356 but this "solution" is specific to the issue with RevState in the zoo. I've got a branch that compiles with ghc-8.10.2, but only because I used CPP to remove the For now it suits my purposes, since I can use that and start working with 8.10. Should I make a PR? It's hardly a real fix, and it's obviously breaking, but it's also better in some ways than not being able to use the lib at all with ghc-8.10. The PR also bumps the upper bound on ghc-prim, otherwise polysemy-zoo won't compile with ghc-8.10.x, and the upper bound on random since that was an important upgrade in random. |
If it's plugin-specific, it's better to rewrite |
Okay! I'l just use my fork for now, then. Thanks! |
Stop-gap for this has been implemented through #66. Not closing this since the underlying bug hasn't been fixed. |
Could a 0.7.0.1 release be pushed in the meantime? |
Done. |
This needs to occur again for 9.0 |
Currently, the zoo won't compile with ghc 8.10.1 because of an upper bound on ghc-prim. It might be as simple as raising the bound. However, when I tried to check via an "allow-newer" in cabal.project, the compiler crashed with a ghc-panic while compiling
Polysemy.RevState
The text was updated successfully, but these errors were encountered: