Skip to content

Move -Werror to travis config#1420

Merged
paf31 merged 3 commits intopurescript:masterfrom
erdeszt:move-werror-to-travis-config
Aug 25, 2015
Merged

Move -Werror to travis config#1420
paf31 merged 3 commits intopurescript:masterfrom
erdeszt:move-werror-to-travis-config

Conversation

@erdeszt
Copy link
Copy Markdown
Contributor

@erdeszt erdeszt commented Aug 24, 2015

As suggested in #1411 moving the -Werror to the travis config from the cabal file.
Not sure though that this is the right way of doing it, I've never used travis before.

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented Aug 24, 2015

👍 Thanks. Let's see what Travis does this time.

@garyb
Copy link
Copy Markdown
Member

garyb commented Aug 24, 2015

This'll conflict with my changes I think, as I removed -Werror also. I guess what we really want is to only run -Werror on the newer GHCs though, right? As otherwise this will suffer from the same problem I had.

@erdeszt
Copy link
Copy Markdown
Contributor Author

erdeszt commented Aug 24, 2015

@garyb I've fixed the only non 7.10 related warning in #1411 so there should be no warnings on earlier versions either(and the travis build for that branch was green for the old versions too, let's see how this one turns out).

@hdgarrood
Copy link
Copy Markdown
Contributor

Why only run -Werror on the newer GHCs? I think I'd rather have it so that there are no warnings on any of the GHCs that we test with.

Also, sorry I didn't think to mention this earlier, but perhaps base-compat might be a bit nicer than CPP all over the place? I think it would also make it easier to deal with any changes in future base releases, if any situations similar to the Foldable/Traversable Proposal arise in the future.

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented Aug 24, 2015

Both of those sound like good ideas to me.

@garyb
Copy link
Copy Markdown
Member

garyb commented Aug 24, 2015

Why only run -Werror on the newer GHCs? I think I'd rather have it so that there are no warnings on any of the GHCs that we test with.

I've already discovered how painful it is to try and track down warnings by waiting 5-10 minutes for Travis to fail so an import can be tweaked... several times :) It wouldn't be so bad if you got all the errors at once.

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented Aug 24, 2015

Wouldn't base-compat help with that though?

@garyb
Copy link
Copy Markdown
Member

garyb commented Aug 24, 2015

Looks like it, yep!

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented Aug 25, 2015

This needs to be merged with master now, sorry.

paf31 added a commit that referenced this pull request Aug 25, 2015
@paf31 paf31 merged commit 5fae353 into purescript:master Aug 25, 2015
@paf31
Copy link
Copy Markdown
Contributor

paf31 commented Aug 25, 2015

Thanks!

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.

4 participants