Skip to content
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

Draft
wants to merge 13 commits into
base: trunk
Choose a base branch
from

Conversation

aryairani
Copy link
Contributor

@aryairani aryairani commented May 21, 2023

Overview

Updates us to ghc 9.4.5 via resolver: nightly-2023-05-20

Todo:

  • look into dependencies that require allow-newer: true
    • NanoID-3.3.0 disallows base 4.17 from ghc 9.4
    • base32-0.2.2.0 disallows text 2.x
    • fuzzyfind-3.0.1 disallows criterion 1.6, text 2.x
    • recover-rtti-0.4.2 disallows aeson 2.1.x, base 4.17, ghc-heap 9.4, primitive 0.8, vector 0.13
    • servant-auth-server disallows monad-time 0.4
    • shellmet-0.0.4.1 disallows base 4.17
  • pr to update enlil https://github.com/unisoncomputing/enlil/pull/223

Implementation notes

  • Remove ' from filenames, for Windows builds
  • Suppressed some new warnings:
    • -Wno-type-equality-requires-operators
    • -Wno-forall-identifier
    • -Wno-incomplete-uni-patterns
    • -Wno-deprecations

Interesting/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

Arya Irani added 2 commits May 20, 2023 22:41
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
@aryairani aryairani marked this pull request as draft May 21, 2023 22:37
@aryairani aryairani force-pushed the stackage-nightly-2023-05-20 branch from 60b76e8 to 3c6d061 Compare May 23, 2023 19:43
@aryairani aryairani changed the title Chore: update stackage resolver to stackage-nightly-2023-05-20 building on stackage-nightly-2023-05-20 (ghc 9.4.5) May 24, 2023
@aryairani aryairani marked this pull request as ready for review May 24, 2023 13:19
@@ -1,6 +1,7 @@
{-# LANGUAGE PatternSynonyms #-}
{-# LANGUAGE TupleSections #-}
{-# LANGUAGE ViewPatterns #-}
{-# OPTIONS_GHC -Wno-forall-identifier #-}
Copy link
Contributor

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.

https://downloads.haskell.org/ghc/latest/docs/users_guide/using-warnings.html?highlight=forall%20identifier#ghc-flag--Wforall-identifier

Copy link
Contributor Author

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.

@aryairani aryairani marked this pull request as draft May 24, 2023 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants