Looking for a recent error reporting change

Hi. In GHC 8.6.5, if I compile a main module that both fails to define `main` and also contains other errors, the other errors are not reported because GHC aborts after realizing that there is no `main`. In GHC 8.10.1, all errors are reported. I'm looking for where this change was made, in the hopes that it's easy to backport to a local branch of GHC 8.6.5. Does anyone know off-hand?

Hi Chris, Maybe you want to look at MR 1806 (https://gitlab.haskell.org/ghc/ghc/- /merge_requests/1806). There I touched the `check is main exported` stuff. There is also MR !1885 for GHC 8.6.2 (https://gitlab.haskell.org /ghc/ghc/-/merge_requests/1885). However this got never merged! Regards Roland Am Sonntag, den 14.06.2020, 09:43 -0400 schrieb Chris Smith:
Hi. In GHC 8.6.5, if I compile a main module that both fails to define `main` and also contains other errors, the other errors are not reported because GHC aborts after realizing that there is no `main`. In GHC 8.10.1, all errors are reported. I'm looking for where this change was made, in the hopes that it's easy to backport to a local branch of GHC 8.6.5. Does anyone know off-hand?
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Roland Senn
Hi Chris, Maybe you want to look at MR 1806 (https://gitlab.haskell.org/ghc/ghc/- /merge_requests/1806). There I touched the `check is main exported` stuff. There is also MR !1885 for GHC 8.6.2 (https://gitlab.haskell.org /ghc/ghc/-/merge_requests/1885). However this got never merged! Regards Roland
Hmm, I'm a bit confused. It looks to me like !1885 was for 8.8 and was merged. Do you mean that we might *also* want to merge for 8.6? FWIW I doubt there will be another release on the 8.6 series. Cheers, - Ben

Is there a reason you want to stick with 8.6.5?
One way to find what you want is to use git-bisect to find the commit that made the change. I think various people have automated setups for this.
Simon
From: ghc-devs

My reason for sticking with 8.6.5 is that I don't yet trust GHCJS with
later GHC versions. Thanks everyone for the pointers and suggestions.
I'll look further into this when I have more time. (Alas, it's not my
full-time job, so that's probably not until the weekend.)
On Mon, Jun 15, 2020 at 5:11 AM Simon Peyton Jones
Is there a reason you want to stick with 8.6.5?
One way to find what you want is to use git-bisect to find the commit that made the change. I think various people have automated setups for this.
Simon
*From:* ghc-devs
*On Behalf Of *Chris Smith *Sent:* 14 June 2020 14:43 *To:* ghc-devs@haskell.org *Subject:* Looking for a recent error reporting change Hi. In GHC 8.6.5, if I compile a main module that both fails to define `main` and also contains other errors, the other errors are not reported because GHC aborts after realizing that there is no `main`. In GHC 8.10.1, all errors are reported. I'm looking for where this change was made, in the hopes that it's easy to backport to a local branch of GHC 8.6.5. Does anyone know off-hand?
participants (4)
-
Ben Gamari
-
Chris Smith
-
Roland Senn
-
Simon Peyton Jones