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

WIP: Enable -Werror in CI #645

Closed
wants to merge 2 commits into from
Closed

Conversation

bgamari
Copy link
Contributor

@bgamari bgamari commented Jun 13, 2019

As noted in #644, this will need changes in haskell-ci to pass.

This will ensure that we don't see future -Wall regressions.
@RyanGlScott
Copy link
Member

An alternative approach to this would be to add local-ghc-options: -Werror to cabal.haskell-ci and then run haskell-ci regenerate. This will ensure that CI is run with -Werror enabled without actually putting -Werror into the .cabal file itself (which cabal check doesn't like).

@treeowl
Copy link
Contributor

treeowl commented Jun 7, 2020

Is this going to go somewhere?

Copy link
Member

@sjakobi sjakobi left a comment

Choose a reason for hiding this comment

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

An alternative approach to this would be to add local-ghc-options: -Werror to cabal.haskell-ci and then run haskell-ci regenerate. This will ensure that CI is run with -Werror enabled without actually putting -Werror into the .cabal file itself (which cabal check doesn't like).

That sounds much better to me.

@sjakobi sjakobi mentioned this pull request Jul 15, 2020
@sjakobi
Copy link
Member

sjakobi commented Jul 15, 2020

As pointed out in #740 (comment), we already build the library with -Werror when GHC >= 8.6.

That seems good enough for me.

I'll tentatively close this, but please re-open if you think there's more to do here.

@sjakobi sjakobi closed this Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants