-
Notifications
You must be signed in to change notification settings - Fork 13
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
fix compilation with ghc-8.4 #36
Conversation
Now, it should compile with ghc >= 7.8. Would you like an update to travis.yml to test against all ghc versions? |
Sounds lovely. Probably best in a separate PR though. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Some minor aesthetic remarks inline.
Why not just use `--resolver`?
…On Thu, Aug 30, 2018, 04:21 Vamshi Surabhi ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In stack-ghc-7.10.3.yaml
<#36 (comment)>:
> @@ -0,0 +1,32 @@
+# For more information, see: https://github.com/commercialhaskell/stack/blob/release/doc/yaml_configuration.md
The reason for these files is to test ginger against all ghc versions with
commands:
stack build --fast --test --stack-yaml=stack-ghc-7.8.4.yaml
stack build --fast --test --stack-yaml=stack-ghc-7.10.3.yaml
stack build --fast --test --stack-yaml=stack-ghc-8.0.2.yaml
stack build --fast --test --stack-yaml=stack-ghc-8.2.2.yaml
stack build --fast
How do you prefer testing against different versions of ghc?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#36 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABXjx4jpqqMyzKjO8aAx-zdVRzhdSXYxks5uV0wogaJpZM4WSLws>
.
|
Thanks again for doing this. BTW., if you like, add yourself to |
This PR only ensures compilation with ghc >= 8.0, we'll need to follow this if support for ghc < 8.0 is needed.