Hi Troels,
Sorry to hear GHC 9 didn't fix your problems! Yes, please open an issue.
Optimising for specific usage patterns might be feasible, although note
that most often it's not the exhaustivity check that is causing problems,
but the check for overlapping patterns.
At the moment the checker
Troels Henriksen writes:
> It is very likely that issue 17386 is the issue. With
>
> {-# OPTIONS_GHC -Wno-overlapping-patterns -Wno-incomplete-patterns
> -Wno-incomplete-uni-patterns -Wno-incomplete-record-updates #-}
>
> my module(s) compile very quickly. I'll wait and see if GHC 9 does
>
They already said something about waiting on dependencies to catch up with
ghc9, IIRC.
On Mon, Feb 15, 2021 at 2:22 PM Carter Schonwald
wrote:
> Don’t forget ghc 9 is already out! :)
>
> On Mon, Feb 15, 2021 at 2:10 PM Troels Henriksen wrote:
>
>> It is very likely that issue 17386 is the
Don’t forget ghc 9 is already out! :)
On Mon, Feb 15, 2021 at 2:10 PM Troels Henriksen wrote:
> It is very likely that issue 17386 is the issue. With
>
> {-# OPTIONS_GHC -Wno-overlapping-patterns -Wno-incomplete-patterns
> -Wno-incomplete-uni-patterns -Wno-incomplete-record-updates #-}
>
> my
It is very likely that issue 17386 is the issue. With
{-# OPTIONS_GHC -Wno-overlapping-patterns -Wno-incomplete-patterns
-Wno-incomplete-uni-patterns -Wno-incomplete-record-updates #-}
my module(s) compile very quickly. I'll wait and see if GHC 9 does
better before I try to create a smaller
Hi,
I'm not sure I see all the context of the conversation, but it is entirely
possible that code with many local constraints regresses the pattern-match
checker (which is accounted to Desugaring in the profile emitted by -v2),
I'm afraid. That simply has to do with the fact that we now actually
Carter Schonwald writes:
> Ccing ghc devs since that’s a better forum perhaps
> Crazy theory:
>
> this is a regression due the the partial changes to pattern matching
> coverage checking in 8.10 that finished / landed in ghc 9
>
> Why:
> Desugaring is when pattern/ case statement translation
Ccing ghc devs since that’s a better forum perhaps
Crazy theory:
this is a regression due the the partial changes to pattern matching
coverage checking in 8.10 that finished / landed in ghc 9
Why:
Desugaring is when pattern/ case statement translation happens I think?
And the only obvious “big
