[ANNOUNCE] GHC 8.8.1 is now available

Hello everyone, The GHC team is pleased to announce the release candidate for GHC 8.8.1. The source distribution, binary distributions, and documentation are available at https://downloads.haskell.org/ghc/8.8.1 This release is the culmination of over 3000 commits by over one hundred contributors and has several new features and numerous bug fixes relative to GHC 8.6: * Visible kind applications are now supported (GHC Proposal #15) * Profiling now works correctly on 64-bit Windows (although still may be problematic on 32-bit Windows due to platform limitations; see #15934) * A new code layout algorithm for amd64's native code generator significantly improving the runtime performance of some kernels * The introduction of a late lambda-lifting pass which may reduce allocations significantly for some programs. * Further work on Trees That Grow, enabling improved code re-use of the Haskell AST in tooling * Users can write `forall` in more contexts (GHC Proposal #7) * The pattern-match checker is now more precise in the presence of strict fields with uninhabited types. * A comprehensive audit of GHC's memory ordering barriers has been performed, resulting in a number of fixes that should significantly improve the reliability of programs on architectures with weakly-ordered memory models (e.g. PowerPC, many ARM and AArch64 implementations). * A long-standing linker limitation rendering GHCi unusable with projects with cyclic symbol dependencies has been fixed (#13786) * Further work on the Hadrian build system * Countless miscellaneous bug-fixes Unfortunately, due to a build issue (#17108) found late in the release process i386 Windows builds are currently unavailable. These will be provided in the coming weeks. As always, if anything looks amiss do let us know. Happy compiling! Cheers, - Ben [1] https://downloads.haskell.org/ghc/8.8.1/docs/html/users_guide/8.8.1-notes.ht...

Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
-- Dan Burton
On Mon, Aug 26, 2019 at 2:25 AM Ben Gamari
Hello everyone,
The GHC team is pleased to announce the release candidate for GHC 8.8.1. The source distribution, binary distributions, and documentation are available at
https://downloads.haskell.org/ghc/8.8.1
This release is the culmination of over 3000 commits by over one hundred contributors and has several new features and numerous bug fixes relative to GHC 8.6:
* Visible kind applications are now supported (GHC Proposal #15)
* Profiling now works correctly on 64-bit Windows (although still may be problematic on 32-bit Windows due to platform limitations; see #15934)
* A new code layout algorithm for amd64's native code generator significantly improving the runtime performance of some kernels
* The introduction of a late lambda-lifting pass which may reduce allocations significantly for some programs.
* Further work on Trees That Grow, enabling improved code re-use of the Haskell AST in tooling
* Users can write `forall` in more contexts (GHC Proposal #7)
* The pattern-match checker is now more precise in the presence of strict fields with uninhabited types.
* A comprehensive audit of GHC's memory ordering barriers has been performed, resulting in a number of fixes that should significantly improve the reliability of programs on architectures with weakly-ordered memory models (e.g. PowerPC, many ARM and AArch64 implementations).
* A long-standing linker limitation rendering GHCi unusable with projects with cyclic symbol dependencies has been fixed (#13786)
* Further work on the Hadrian build system
* Countless miscellaneous bug-fixes
Unfortunately, due to a build issue (#17108) found late in the release process i386 Windows builds are currently unavailable. These will be provided in the coming weeks.
As always, if anything looks amiss do let us know.
Happy compiling!
Cheers,
- Ben
[1] https://downloads.haskell.org/ghc/8.8.1/docs/html/users_guide/8.8.1-notes.ht... _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
Dan Burton
writes: Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
Cheers,
- Ben _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

On October 3, 2019 11:23:26 PM EDT, David Feuer
Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
wrote: Dan Burton
writes: Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
The issue (#17246) is still blocked on others. One issue is that uploading the 8.8 boot packages first requires that hackage.haskell.org to be upgraded and no Hackage admin has had time to do this yet.
Cheers, - Ben _______________________________________________
Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Any updates? It's a crisis that the standard library is unavailable on
Hackage...
2019年10月4日(金) 12:30 Ben Gamari
Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
wrote: Dan Burton
writes: Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
The issue (#17246) is still blocked on others. One issue is that uploading
On October 3, 2019 11:23:26 PM EDT, David Feuer
wrote: the 8.8 boot packages first requires that hackage.haskell.org to be upgraded and no Hackage admin has had time to do this yet. Cheers,
- Ben _______________________________________________
Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Do you mean because you want to read the documentation, or is there some other reason that base ought to be on Hackage? It's not installable from there, as far as I know. On Tue, Oct 29, 2019 at 02:03:02PM +0900, Fumiaki Kinoshita wrote:
Any updates? It's a crisis that the standard library is unavailable on Hackage...
2019年10月4日(金) 12:30 Ben Gamari
: Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
wrote: Dan Burton
writes: Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
The issue (#17246) is still blocked on others. One issue is that uploading
On October 3, 2019 11:23:26 PM EDT, David Feuer
wrote: the 8.8 boot packages first requires that hackage.haskell.org to be upgraded and no Hackage admin has had time to do this yet.

Documentation is helpful, yes. On Tue, Oct 29, 2019 at 5:06 PM Tom Ellis < tom-lists-haskell-cafe-2017@jaguarpaw.co.uk> wrote:
Do you mean because you want to read the documentation, or is there some other reason that base ought to be on Hackage? It's not installable from there, as far as I know.
On Tue, Oct 29, 2019 at 02:03:02PM +0900, Fumiaki Kinoshita wrote:
Any updates? It's a crisis that the standard library is unavailable on Hackage...
2019年10月4日(金) 12:30 Ben Gamari
: On October 3, 2019 11:23:26 PM EDT, David Feuer
Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
wrote: Dan Burton
writes: Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage?
Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
The issue (#17246) is still blocked on others. One issue is that uploading
wrote: the 8.8 boot packages first requires that hackage.haskell.org to be upgraded and no Hackage admin has had time to do this yet.
Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- brandon s allbery kf8nh allbery.b@gmail.com

There is also no ghc package entry for 8.8.1, unfortunately.
--
Best, Artem
On Tue, 29 Oct 2019 at 17:10, Brandon Allbery
Documentation is helpful, yes.
On Tue, Oct 29, 2019 at 5:06 PM Tom Ellis < tom-lists-haskell-cafe-2017@jaguarpaw.co.uk> wrote:
Do you mean because you want to read the documentation, or is there some other reason that base ought to be on Hackage? It's not installable from there, as far as I know.
On Tue, Oct 29, 2019 at 02:03:02PM +0900, Fumiaki Kinoshita wrote:
Any updates? It's a crisis that the standard library is unavailable on Hackage...
2019年10月4日(金) 12:30 Ben Gamari
: On October 3, 2019 11:23:26 PM EDT, David Feuer <
david.feuer@gmail.com>
Any news?
On Tue, Sep 24, 2019, 5:22 PM Ben Gamari
wrote: Dan Burton
writes: > Will base-4.13.0.0 (which ships with ghc 8.8) be uploaded to hackage? > Yes, although it's currently waiting for someone with maintainer rights for `base`, et al to push them. I have requested access myself although haven't yet heard back.
The issue (#17246) is still blocked on others. One issue is that uploading
wrote: the 8.8 boot packages first requires that hackage.haskell.org to be upgraded and no Hackage admin has had time to do this yet.
Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- brandon s allbery kf8nh allbery.b@gmail.com _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Fumiaki Kinoshita
Any updates? It's a crisis that the standard library is unavailable on Hackage...
I agree; having a release out for two months without full representation on Hackage is quite suboptimal. Unfortunately, the Hackage trustees have quite a bit on their plate. I have spoken to Herbert, who usually handles the boot library uploads, several times about this and I have gleaned that the situation is as follows: * hackage-server needs to be updated to Cabal-3, tested, and the deployment updated before the remaining boot packages can be uploaded (admittedly I'm not familiar with the technical reasons for this dependency, but this is what I have been told) This is an area where a dedicated volunteer could help enormously. hackage-server is just another Haskell program (albeit one lacking contributors); all that updating it would require is time. * Herbert has said that he also wants to take a careful look through the packages before uploading them to ensure that no serious mistakes are committed permanently to the Hackage cache For what it is worth, I have asked several times whether I can help with the upload process but have been turned down repeatedly. I can't claim that I fully understand the reasoning behind this, but I can nevertheless respect the decision. I also am reluctant to make demands on the time of others. In particular, the trustees are all volunteers with lives and jobs who carry out often quite thankless work. We all owe them an enormous debt of gratitude for maintaining the infrastructure that we rely on every day, usually without thinking twice. I wish I could offer a clever idea for accelerating this process; sadly, the problem seems to be an unfortunate combination of technical dependencies (e.g. the boot library upload requiring a hackage-server update), a lack of contributors to help resolve this dependency, and a small but very busy set of core contributors. It seems to me that it would be best if we could grow the set of people who are regularly involved in Hackage administration to avoid this happening in the future. However, this will require that people who don't mind doing a bit of less-than-thrilling work (e.g. updating hackage-server) pitch in. Cheers, - Ben

Thank you for clarifying the situation. I'm not sure if I understand the
reasoning behind the dependency either, but I'll see if I can help with
hackage-server.
2019年10月30日(水) 12:11 Ben Gamari
Fumiaki Kinoshita
writes: Any updates? It's a crisis that the standard library is unavailable on Hackage...
I agree; having a release out for two months without full representation on Hackage is quite suboptimal. Unfortunately, the Hackage trustees have quite a bit on their plate. I have spoken to Herbert, who usually handles the boot library uploads, several times about this and I have gleaned that the situation is as follows:
* hackage-server needs to be updated to Cabal-3, tested, and the deployment updated before the remaining boot packages can be uploaded (admittedly I'm not familiar with the technical reasons for this dependency, but this is what I have been told)
This is an area where a dedicated volunteer could help enormously. hackage-server is just another Haskell program (albeit one lacking contributors); all that updating it would require is time.
* Herbert has said that he also wants to take a careful look through the packages before uploading them to ensure that no serious mistakes are committed permanently to the Hackage cache
For what it is worth, I have asked several times whether I can help with the upload process but have been turned down repeatedly. I can't claim that I fully understand the reasoning behind this, but I can nevertheless respect the decision.
I also am reluctant to make demands on the time of others. In particular, the trustees are all volunteers with lives and jobs who carry out often quite thankless work. We all owe them an enormous debt of gratitude for maintaining the infrastructure that we rely on every day, usually without thinking twice.
I wish I could offer a clever idea for accelerating this process; sadly, the problem seems to be an unfortunate combination of technical dependencies (e.g. the boot library upload requiring a hackage-server update), a lack of contributors to help resolve this dependency, and a small but very busy set of core contributors.
It seems to me that it would be best if we could grow the set of people who are regularly involved in Hackage administration to avoid this happening in the future. However, this will require that people who don't mind doing a bit of less-than-thrilling work (e.g. updating hackage-server) pitch in.
Cheers,
- Ben

On Tue, Oct 29, 2019 at 11:11:04PM -0400, Ben Gamari wrote:
* hackage-server needs to be updated to Cabal-3, tested, and the deployment updated before the remaining boot packages can be uploaded (admittedly I'm not familiar with the technical reasons for this dependency, but this is what I have been told)
Perhaps Herbert could pitch in with an explanation because I think a lot of people will be feeling quite puzzled at this point.

My questions at this point are: * What are the reasons that hackage-server must be upgraded to Cabal 3? * What are the reasons that make this upgrade difficult? * Can publishing to hackage be considered a proper part of the ghc release process in the future? On Wed, Oct 30, 2019, 07:30 Tom Ellis < tom-lists-haskell-cafe-2017@jaguarpaw.co.uk> wrote:
On Tue, Oct 29, 2019 at 11:11:04PM -0400, Ben Gamari wrote:
* hackage-server needs to be updated to Cabal-3, tested, and the deployment updated before the remaining boot packages can be uploaded (admittedly I'm not familiar with the technical reasons for this dependency, but this is what I have been told)
Perhaps Herbert could pitch in with an explanation because I think a lot of people will be feeling quite puzzled at this point. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Dan Burton
My questions at this point are:
* What are the reasons that hackage-server must be upgraded to Cabal 3?
I'll leave this to Herbert as I am also not clear on this point. None of the 8.8.1 boot packages should be relying on Cabal 3 syntax in their .cabal files so I'm not sure what specifically gives rise to this dependency.
* What are the reasons that make this upgrade difficult?
Cabal 3 does change quite a bit. In response to the number of requests to get this un-stuck I put in some work [1] this week and last to start the upgrade. Indeed the process is non-trivial and requires touching a lot of code. Nearly all of this churn is due to the removal of the Text typeclass in favor of the Parsec and Pretty typeclasses. These changes are generally quite mechanical but do take time.
* Can publishing to hackage be considered a proper part of the ghc release process in the future?
I am quite willing to handle the uploads as part of the release process if this is the direction we decide to take. Cheers, - Ben [1] https://github.com/bgamari/hackage-server/tree/cabal-3

I just realised another reason why this upload is important - I use
http://packdeps.haskellers.com/ RSS feed support to notify me when any of
my packages have out of date dependencies. Unfortunately, I haven't
actually got any notifications about my packages not building with GHC 8.8,
so I'm having to rely on users reporting issues.
On Wed, 30 Oct 2019, 11:01 pm Ben Gamari,
Dan Burton
writes: My questions at this point are:
* What are the reasons that hackage-server must be upgraded to Cabal 3?
I'll leave this to Herbert as I am also not clear on this point. None of the 8.8.1 boot packages should be relying on Cabal 3 syntax in their .cabal files so I'm not sure what specifically gives rise to this dependency.
* What are the reasons that make this upgrade difficult?
Cabal 3 does change quite a bit. In response to the number of requests to get this un-stuck I put in some work [1] this week and last to start the upgrade. Indeed the process is non-trivial and requires touching a lot of code.
Nearly all of this churn is due to the removal of the Text typeclass in favor of the Parsec and Pretty typeclasses. These changes are generally quite mechanical but do take time.
* Can publishing to hackage be considered a proper part of the ghc release process in the future?
I am quite willing to handle the uploads as part of the release process if this is the direction we decide to take.
Cheers,
- Ben
[1] https://github.com/bgamari/hackage-server/tree/cabal-3 _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
participants (8)
-
Artem Pelenitsyn
-
Ben Gamari
-
Brandon Allbery
-
Dan Burton
-
David Feuer
-
Fumiaki Kinoshita
-
Oliver Charles
-
Tom Ellis