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

Update to latest stack version and fix warnings. #41

Conversation

cdepillabout
Copy link

This PR includes a couple different changes:

  • Updates the stack version from 3.20 to 6.11.
  • Removes any support for ghc versions less than 7.10.
    • It looks like there was originally support for 7.8, but origin/master currently does not compile on 7.8, so everything about 7.8 was removed.
  • Gets rid of all compiler warnings.
  • Adds a .travis.yml. You can checkout the tests here. It's currently being tested on a couple recent versions of stackage, along with raw cabal. Everything is passing (other than GHC HEAD).
    • The .travis.yml was adapted from here.
  • Adds a simple README.md.

@cdepillabout
Copy link
Author

I think I'm going to send a could more PRs over the next week. I might also want the other open PR merged in.

@meteficha If you wanted to make me a member for fb (just like ig), I could go ahead a do a new release when I get my changes in.

, http-types
, http-conduit >= 2.0 && < 2.2
, attoparsec >= 0.10.4 && < 0.14
, unordered-containers
, aeson >= 0.5
Copy link

Choose a reason for hiding this comment

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

This should be bumped up to aeson >= 0.7 since that is when the function encodeToTextBuilder was introduced (which you use in this PR)

@bitc
Copy link

bitc commented Sep 30, 2016

@meteficha +1 to the above for giving @cdepillabout access to do a release :)

@cdepillabout
Copy link
Author

@bitc Thanks for the heads-up! I've bumped the aeson dependency.

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.

2 participants