You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing warnings like these while building with GHC 8.4 and 8.6 both:
lib/DhallToCabal.hs:656:9: warning: [-Woverlapping-patterns]
Pattern match is redundant
In a case alternative: Expr.App "withinVersion" components -> ...
|
656 | Expr.App "withinVersion" components ->
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
lib/DhallToCabal.hs:659:9: warning: [-Woverlapping-patterns]
Pattern match is redundant
In a case alternative:
Expr.App "majorBoundVersion" components -> ...
|
659 | Expr.App "majorBoundVersion" components ->
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
lib/DhallToCabal.hs:776:9: warning: [-Woverlapping-patterns]
Pattern match is redundant
In a case alternative: Expr.App (Expr.App "or" a) b -> ...
|
776 | Expr.App ( Expr.App "or" a ) b ->
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
Experimentally, I tried removing one of the complained-about cases, but that broke the tests, as I'd expected from looking at the code. GHC's pattern coverage checker is evidently drawing a false conclusion, but I'm not sure if it's somehow being led astray or if it's a legitimate compiler bug.
I can't find an obviously responsible ticket in GHC's trac that'd be causing this behaviour. Does anyone have a clue? If not, the next step is to try to minimise the example and verify that it's a GHC bug.
Also, I should note that I think they started with 8801086: I haven't bisected, but that's what git blame points to. I can't see anything obviously amiss about the commit, though.
The text was updated successfully, but these errors were encountered:
I'm seeing warnings like these while building with GHC 8.4 and 8.6 both:
Experimentally, I tried removing one of the complained-about cases, but that broke the tests, as I'd expected from looking at the code. GHC's pattern coverage checker is evidently drawing a false conclusion, but I'm not sure if it's somehow being led astray or if it's a legitimate compiler bug.
I can't find an obviously responsible ticket in GHC's trac that'd be causing this behaviour. Does anyone have a clue? If not, the next step is to try to minimise the example and verify that it's a GHC bug.
Also, I should note that I think they started with 8801086: I haven't bisected, but that's what
git blame
points to. I can't see anything obviously amiss about the commit, though.The text was updated successfully, but these errors were encountered: