Stackage lts 7.19 #268
Stackage lts 7.19 #268
Conversation
| @@ -40,7 +40,7 @@ import qualified Data.Functor.Identity as I | |||
| -- 'ProductProfunctor') in @s@ and @t@. It is unclear at this point | |||
| -- whether we want the same @Traversal@ laws to hold or not. Our use | |||
| -- cases may be much more general. | |||
| data PackMap a b s t = PackMap (Applicative f => | |||
| data PackMap a b s t = PackMap (forall f. Applicative f => | |||
There was a problem hiding this comment.
I'm not exactly sure which change in the compiler necessitated this change. However it appears to be backwards compatible, so I don't see a problem with it.
There was a problem hiding this comment.
Yeah, that's something that had to change in Opaleye a while ago but I didn't fix the sqlite version at the same time.
There was a problem hiding this comment.
@WillSewell Are you actually using opaleye-sqlite? I'm not sure how widely used it is.
There was a problem hiding this comment.
No I'm not, but I thought I'd update the deps for it since I was updating the stack.yaml resolver version anyway.
|
Thanks Will, this is great. |
|
No problem. Thanks for merging :) It would be good if this could be released soon, otherwise |
|
I uploaded this last night. Is that sufficient? |
|
Ah yes. I was looking for a new version in the GitHub repo, but it looks like you haven't pushed the commit where you bumped the version yet. |
|
Good point. I'm continually stymied by Anyway, the new version is now on github master. |
I wanted to make this compatible with
aeson-1.1.*. In doing so I did a stackage lts upgrade because it was quite out of date. I also updated the relevant upper bounds.I can remove the last commit if you would prefer (and you are happy with the tests passing).