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

Make it build with ghc 9.12 #1406

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Make it build with ghc 9.12 #1406

wants to merge 4 commits into from

Conversation

erikd
Copy link
Contributor

@erikd erikd commented Feb 28, 2025

Description

Make it build with ghc 9.12
Also note that:

  • New code should be properly tested (even if it does not add new features).
  • The fix for a regression should include a test that reproduces said regression.

No longer needed. GHC has been deriving this typeclass for some time
and ghc-9.12 now warns about it being redundant.
@erikd erikd force-pushed the erikd/ghc-9.12 branch 2 times, most recently from b9dd4f4 to 0c19547 Compare February 28, 2025 04:06
@erikd erikd force-pushed the erikd/ghc-9.12 branch 2 times, most recently from 7a46308 to e5fad05 Compare February 28, 2025 04:15
Copy link
Contributor

@jasagredo jasagredo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR looks good, but I wonder if we want to merge it with those allow-newer.

Also I'd rather wait until the 10.3 branch is rebased onto latest main, before merging this one

Copy link
Contributor

@nfrisby nfrisby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the changes look mild (🙌) except that ref=for-stackackage in the haskell.nix declaration.

@@ -16,7 +16,7 @@
inputs.hackage.follows = "hackageNix";
};
hackageNix = {
url = "github:input-output-hk/hackage.nix";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not familiar with the broader consequences of this change. The haskell.nix repo says:

The for-stackage branch also contains all cabal expressions from hackage.org as nix expressions.

This branch is used when working with stack projects in haskell.nix.

Could you summarize the potential reasons to not use it? And what is requiring its use here? The Consensus build process (eg CI) generally doesn't involve stack.

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.

3 participants