New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
building on stackage-nightly-2023-05-20 (ghc 9.4.5) #4009
base: trunk
Are you sure you want to change the base?
Conversation
moved to ki 1.0.1.0 for greater build compatibility newly suppressed warnings in a few files - forall identifier - cases identifier (dunno how to suppress this which didn't show up as a warning) - type equality requires operators - deprecations
60b76e8
to
3c6d061
Compare
@@ -1,6 +1,7 @@ | |||
{-# LANGUAGE PatternSynonyms #-} | |||
{-# LANGUAGE TupleSections #-} | |||
{-# LANGUAGE ViewPatterns #-} | |||
{-# OPTIONS_GHC -Wno-forall-identifier #-} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could (carefully) s/forall/forAll
as recommended by the manual instead? 😄 Looks like this will be come a non-optional error in a future release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I should've called it out better, this is just a temporary measure since it will become mandatory soon. forAll
sounds like a good fix.
Overview
Updates us to ghc 9.4.5 via
resolver: nightly-2023-05-20
Todo:
allow-newer: true
Implementation notes
'
from filenames, for Windows buildsInteresting/controversial decisions
Could use better names than
ReferentG
,SearchResult2
etc.; though, the lack of better names is why these have been named with'
for 5 years.Test coverage
Covered hopefully by existing tests
Loose ends
Dealing with all the newly suppressed warnings