-
Notifications
You must be signed in to change notification settings - Fork 1
Support GHC 9.10 #5
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
Conversation
ping @phadej been cabal jailbreaking for a plethora of packages with no issues |
I'll probably comeback to |
OK. I'm fairly certain the fix is only a base bump and Cabal revision (edit: for each package, but I only use defun-core personally). Let me know if you don't want to merge this, and I'll close and keep working around. Thanks regardless for the package :) |
GHC 9.12.1 is released and 9.12.2 (which should fix the runtime bug) is maybe a week away. ping @phadej |
GHC-9.12.2 should drop tomorrow (with hopefully no big delays to get available through I"m very aware of that, thanks. |
Right, sorry for the bluntness. I meant this as a reply to
I have a handful of libraries that depend on some type-level work using defun-core and hoping to remove my defun jailbreaks :) |
Apparently the message was 12th week, i.e. week 17.3..23.3; well I'm busy that one, and the one after that. If we had to wait for bug fix release over three months, we can wait few weeks on top of that. Sorry for inconvenience. EDIT: I will make an update for GHC-9.12 then; but I'm very likely to skip the GHC-9.14. So next updates after this will be tentatively in 2026. |
I run into haskell/cabal#10836 elsewhere, and TBH it ate all the current motivation to work for GHC-9.12 support. I really don't want to work around tool limitations. Hopefully I don't ask for too much when I expect tools to work (not worse then previous versions). |
I understand maintenance for lots of pkgs is time-consuming. I shall be patient. Thanks again for defun. |
defun builds fine on GHC 9.10 with updated base bounds. I also jailbroke it for a package I wrote that depends on it, and it seems to be fine (testing currently).