[Haskell-cafe] [ANNOUNCE] GHC 8.2.2 release candidate 2

jpaugh at gmx.com jpaugh at gmx.com
Sun Nov 5 14:37:48 UTC 2017

A better approach might be to develop a "machine-readable" output format which then is kept stable, and can be enabled with a flag. Git has a similar solution.

It would be a shame to avoid changes which make the user experience better simply because other projects cannot sync their development cycle, especially if those projects are not universally used or required.


On November 5, 2017 6:56:53 AM CST, Sven Panne <svenpanne at gmail.com> wrote:
>This is not an issue about 8.2.2 per se, but 8.2 changes in general:
>discussions on Haskell Cafe showed serious problems with Emacs'
>haskell-mode due to some ad hoc changes like
>https://phabricator.haskell.org/D3651. Related GitHub issues:
>   https://github.com/haskell/haskell-mode/issues/1553
>   https://github.com/haskell/haskell-mode/issues/1496
>It should be noted that the output of GHC(i) is actually part of GHC's
>interface, so in this light, there have been some breaking changes,
>probably unintended, but nevertheless. So my question is: Is there a
>to revert some of these ad hoc changes and/or add some flags to get the
>behavior back? I guess that Emacs + haskell-mode is one of the most
>important IDEs, so it would be a pity to worsen the situation there.
>I'm quite aware that it is very late in the release cycle, but it would
>extremely nice if there was something which can be done. In the future
>might make sense to co-operate with the haskell-mode team a bit more,
>perhaps adding some tests regarding the required output format etc. to
>GHC's test suite.
>   S.

Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20171105/db8b017f/attachment.html>

More information about the Haskell-Cafe mailing list