Update persistent, make buildable with ghc 8.6#1561
Merged
snoyberg merged 7 commits intoyesodweb:masterfrom Oct 14, 2018
Merged
Update persistent, make buildable with ghc 8.6#1561snoyberg merged 7 commits intoyesodweb:masterfrom
snoyberg merged 7 commits intoyesodweb:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
This was accomplished by making pattern match failures explicitly call
liftIO $ fail "$msg", instead of the formerly implicit call tofailon irrefutable pattern matches. Further improvements may be desired, but I believe this change at least preserves (and makes more explicit) the pre-existing behavior.Tests
I have successfully built & run tests on these changes using the current
stack.yamlas follows:I have additionally built & run tests using the following
stack.yamlwhich uses ghc 8.6 as well as persistent-2.9.2 (& others in that repo) from source, (as well as a small tweak on the constraints onemail-validate) like so:Checklists
Before submitting your PR, check that you've:
[ ] Documented new APIs with Haddock markup[ ] Added@sincedeclarations to the Haddocks for new, public APIsAfter submitting your PR: