
tl;dr: GHC 8.0.2 is coming, however there are a number of issues we would like to see resolved. Consequently it's not entirely clear when it will arrive, but if things go well it may be as early as this Friday. Hello everyone, Over the past few weeks I've been making preparations for the coming 8.0.2 release. I've merged a few more patches to the stable branch in response to last week's call for merge requests, bringing the total up to 180 commits since 8.0.1. At this point there are only a couple things that remain to be cleared up, * #12220, #12533: These are unfortunate behaviors of default signatures, #12220 being an interaction with type applications and #12533 being an obscure corner case. While we have a fix for these (d2958bd0), the fix changes the behavior of the typechecker's inaccessible code check, breaking some code on Hackage; this is documented as #12466. There are some tricky unresolved questions here regarding how we want the inaccessible code here to behave. At the moment I am leaning towards simply punting these off to 8.2.1. If you would like to see them fixed in 8.0.2, please say so. Moreover, please contribute your thoughts on #12466 as resolving the remaining questions on that ticket is a prerequisite for merging the fix for #12220. * #12954: Currently Haddock does not produce documentation for bundled pattern synonyms. There is a pull request [1] that may fix this but it is currently needing reviewers. It would be great to fix this for 8.0.2, but ultimately someone is going to need to finish this up. * #10986: This is a rather unfortunate leak of temporary files which we would ideally fix since it can produce rather large temporary directories on the user's system. * #12519: Haddock inexplicably forgets to render the class members of Eq and Ord. It would be great if someone could get to the bottom of this. * #12433 is a rather nasty correctness bug which currently has no resolution. * #11819: There are still a number of full validation issues which would be nice to sort out. I would like to be able to say that we have a concrete timeline for a 8.0.2 release and I was originally planning to propose a candidate source release for late this week, however in light of the the large number of unresolved issues, I think it would be unwise to commit to this timeframe. I'll say that the candidate source tarball could come as early as Friday, although sometime next week is far more likely. As always, any help that you could offer on any of the above issues would be greatly appreciated. Cheers, - Ben [1] https://github.com/haskell/haddock/pull/494/commits/7984c8fb8f238793641a419c...

I imagine I have completely missed the boat on this one, but would like to test the waters on including the following [1] patch --------------------------------------------- Add hook for creating ghci external interpreter The external interpreter is launched by calling 'System.Process.createProcess' with a 'CreateProcess' parameter. The current value for this has the 'std_in', 'std_out' and 'std_err' fields use the default of 'Inherit', meaning that the remote interpreter shares the stdio with the original ghc/ghci process. This patch introduces a new hook to the DynFlags, which has an opportunity to override the 'CreateProcess' fields, launch the process, and retrieve the stdio handles actually used. So if a ghci external interpreter session is launched from the GHC API the stdio can be redirected if required, which is useful for tooling/IDE integration. ----------------------------- It is not behaviour-changing unless the hook is actually used, but does make a change to Hooks and hence DynFlags. I think it can potentially make a lot more options available for IDE tooling, and it would be great to have it available in GHC 8.0.x already. Alan [1] https://github.com/alanz/ghc/commit/6225d94056400c525a2b710aa31a74b5ea1d5f62

Alan & Kim Zimmerman
I imagine I have completely missed the boat on this one, but would like to test the waters on including the following [1] patch
Given that it's a pretty small patch and seems like it would be quite handy I'd certainly willing to consider it. Let's first get it merged into master though. Can you put it up on Phabricator? Cheers, - Ben

Are there any updates on 8.0.2? Thanks!
To put things in the perspective of yesod-based commercial GHC users:
Due to #12130, GHC 8 is useless to us until 8.0.2. So for us this is
the most important GHC release in years.
In our particular case, our products are now being held back in very
concrete ways, because there are some critical libraries we can no
longer update. The ecosystem has moved on to GHC 8, and we have been
left behind.
In anticipation of the release, and after the delay in the RC builds,
we are now trying to compile GHC from source on multiple platforms
just so that we can already start on all the infrastructure work we
need to do for this major upgrade. That way we hopefully will be able
to sprint from the gate as soon as there is an actual release. But
obviously we would prefer to use RC builds for that.
Thanks to all on the GHC team for all your great work!
Yitz
On Wed, Sep 7, 2016 at 7:28 PM, Ben Gamari
tl;dr: GHC 8.0.2 is coming, however there are a number of issues we would like to see resolved. Consequently it's not entirely clear when it will arrive, but if things go well it may be as early as this Friday.
Hello everyone,
Over the past few weeks I've been making preparations for the coming 8.0.2 release. I've merged a few more patches to the stable branch in response to last week's call for merge requests, bringing the total up to 180 commits since 8.0.1.
At this point there are only a couple things that remain to be cleared up,
* #12220, #12533: These are unfortunate behaviors of default signatures, #12220 being an interaction with type applications and #12533 being an obscure corner case. While we have a fix for these (d2958bd0), the fix changes the behavior of the typechecker's inaccessible code check, breaking some code on Hackage; this is documented as #12466. There are some tricky unresolved questions here regarding how we want the inaccessible code here to behave.
At the moment I am leaning towards simply punting these off to 8.2.1. If you would like to see them fixed in 8.0.2, please say so. Moreover, please contribute your thoughts on #12466 as resolving the remaining questions on that ticket is a prerequisite for merging the fix for #12220.
* #12954: Currently Haddock does not produce documentation for bundled pattern synonyms. There is a pull request [1] that may fix this but it is currently needing reviewers. It would be great to fix this for 8.0.2, but ultimately someone is going to need to finish this up.
* #10986: This is a rather unfortunate leak of temporary files which we would ideally fix since it can produce rather large temporary directories on the user's system.
* #12519: Haddock inexplicably forgets to render the class members of Eq and Ord. It would be great if someone could get to the bottom of this.
* #12433 is a rather nasty correctness bug which currently has no resolution.
* #11819: There are still a number of full validation issues which would be nice to sort out.
I would like to be able to say that we have a concrete timeline for a 8.0.2 release and I was originally planning to propose a candidate source release for late this week, however in light of the the large number of unresolved issues, I think it would be unwise to commit to this timeframe. I'll say that the candidate source tarball could come as early as Friday, although sometime next week is far more likely.
As always, any help that you could offer on any of the above issues would be greatly appreciated.
Cheers,
- Ben
[1] https://github.com/haskell/haddock/pull/494/commits/7984c8fb8f238793641a419c...
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Yitzchak Gale
Are there any updates on 8.0.2? Thanks!
To put things in the perspective of yesod-based commercial GHC users: Due to #12130, GHC 8 is useless to us until 8.0.2. So for us this is the most important GHC release in years.
At the moment I'm trying to work out some issues with merging #12466. This is the last issue on my queue other than doing basic build testing on the other architectures. Sadly next week I'll be at ICFP so it's unlikely that much progress will be made until the following week.
In our particular case, our products are now being held back in very concrete ways, because there are some critical libraries we can no longer update. The ecosystem has moved on to GHC 8, and we have been left behind.
Thanks for the data-point! It's very helpful for prioritization to know these sorts of things. Don't hesitate to bring this up this sort of thing early in the future.
In anticipation of the release, and after the delay in the RC builds, we are now trying to compile GHC from source on multiple platforms just so that we can already start on all the infrastructure work we need to do for this major upgrade. That way we hopefully will be able to sprint from the gate as soon as there is an actual release. But obviously we would prefer to use RC builds for that.
Thanks to all on the GHC team for all your great work!
Thanks Yitz! Cheers, - Ben

Ben, thanks much for the update.
It's not sad that you'll be at ICFP - I wish I could be there too! :)
Historically ICFP has provided much of the juice that GHC runs on.
Enjoy, and good luck with the release.
Regards,
Yitz
On Sun, Sep 18, 2016 at 4:07 PM, Ben Gamari
Yitzchak Gale
writes: Are there any updates on 8.0.2? Thanks!
To put things in the perspective of yesod-based commercial GHC users: Due to #12130, GHC 8 is useless to us until 8.0.2. So for us this is the most important GHC release in years.
At the moment I'm trying to work out some issues with merging #12466. This is the last issue on my queue other than doing basic build testing on the other architectures. Sadly next week I'll be at ICFP so it's unlikely that much progress will be made until the following week.
In our particular case, our products are now being held back in very concrete ways, because there are some critical libraries we can no longer update. The ecosystem has moved on to GHC 8, and we have been left behind.
Thanks for the data-point! It's very helpful for prioritization to know these sorts of things. Don't hesitate to bring this up this sort of thing early in the future.
In anticipation of the release, and after the delay in the RC builds, we are now trying to compile GHC from source on multiple platforms just so that we can already start on all the infrastructure work we need to do for this major upgrade. That way we hopefully will be able to sprint from the gate as soon as there is an actual release. But obviously we would prefer to use RC builds for that.
Thanks to all on the GHC team for all your great work!
Thanks Yitz!
Cheers,
- Ben

i hit a funny issue with the near term -hb patch, i'll try to track it
down, but reverting it allowed me to get a mac build of 8.0 master in shape
On Sun, Sep 18, 2016 at 9:16 AM, Yitzchak Gale
Ben, thanks much for the update.
It's not sad that you'll be at ICFP - I wish I could be there too! :) Historically ICFP has provided much of the juice that GHC runs on. Enjoy, and good luck with the release.
Regards, Yitz
On Sun, Sep 18, 2016 at 4:07 PM, Ben Gamari
wrote: Yitzchak Gale
writes: Are there any updates on 8.0.2? Thanks!
To put things in the perspective of yesod-based commercial GHC users: Due to #12130, GHC 8 is useless to us until 8.0.2. So for us this is the most important GHC release in years.
At the moment I'm trying to work out some issues with merging #12466. This is the last issue on my queue other than doing basic build testing on the other architectures. Sadly next week I'll be at ICFP so it's unlikely that much progress will be made until the following week.
In our particular case, our products are now being held back in very concrete ways, because there are some critical libraries we can no longer update. The ecosystem has moved on to GHC 8, and we have been left behind.
Thanks for the data-point! It's very helpful for prioritization to know these sorts of things. Don't hesitate to bring this up this sort of thing early in the future.
In anticipation of the release, and after the delay in the RC builds, we are now trying to compile GHC from source on multiple platforms just so that we can already start on all the infrastructure work we need to do for this major upgrade. That way we hopefully will be able to sprint from the gate as soon as there is an actual release. But obviously we would prefer to use RC builds for that.
Thanks to all on the GHC team for all your great work!
Thanks Yitz!
Cheers,
- Ben
ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
participants (4)
-
Alan & Kim Zimmerman
-
Ben Gamari
-
Carter Schonwald
-
Yitzchak Gale