-
Notifications
You must be signed in to change notification settings - Fork 30
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
Recommending GHC 9.6.x #220
Comments
Stackage LTS 22 for GHC 9.6 still has not closed (LTS 22.39 released last week), but soon will:
Once LTS development moves to GHC 9.8 I think 9.6 will be as stable as it gets and should get the status of the recommended GHC (or it will never get it). |
The FreeBSD bugfix has not been backported. If GHC HQ doesn't do it, then I will. Which will take some time. |
I meant to write this elsewhere (in Discourse), but I think it would be reasonable to have different default versions for different platforms when necessary. It doesn't make sense to hold back tier 1 platforms indefinitely, because of tier 2 or lower. Basically "everyone" considers ghc-9.6 stable at this point. |
I have explained this in some detail a couple of times in my talks: That is specifically against the philosophy of ghcup. One of the major use cases of the 'recommended' tag is a university course of ~200 students doing some exercises. You definitely do not want different versions across platforms. The default installation should deliver the same toolchain on all platforms. So the 'recommended' tag isn't meant to be a "this release is good on some platforms", but a "this works equally well across most platforms". If GHC cannot deliver a consistent experience across platforms, then that's definitely a problem for us, but it also allows us to push back and say "go fix this". |
@AndreasPK what is the status of the RTS bugfix backport? Otherwise I will have to consider another downstream release (since it's a runtime bug... fixing in-place won't cut it). |
@hasufell that issue is, as far as we know, fixed in |
Related discussions:
The text was updated successfully, but these errors were encountered: