-
Notifications
You must be signed in to change notification settings - Fork 82
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
Can no longer derive ParseTime instance #119
Comments
I hadn't really intended to allow people to create their own instances of Does it help to import |
yes, I'm not able to derive
although this relies on internals that you mentioned might change. |
Well, that's not ideal. I think newtype-deriving should work. Probably the simplest thing would be to replace the |
Fixed for 1.10 |
@AshleyYakeley thanks for fixing this! Is there an ETA for a release of 1.10 on Hackage (or even better, Stackage?) Context: I'm trying to build https://github.com/kubernetes-client/haskell on the new GHC 8.8 and running into this issue. |
@thomasjm 1.10 is now up on Hackage. Stackage policy is to keep core library versions matched with the ones in GHC, so it won't be in Stackage until it's first in GHC (probably 8.10) and then there's a new LTS for that version of GHC. In the mean time, however, you can add |
It turns out the instance you mentioned @jonschoning actually does not work properly. I introduced it to a OpenAPI-generated library so that I could build against the latest I'm working with the Kubernetes library, and found it failed to parse a string like Not sure why this happens. However, it doesn't seem necessary to actually derive a |
I upgraded from
time-1.8.0.2
totime-1.9.3
, and found this causes some code that was working withtime-1.8.0.2
to break when deriving an instance forParseTime
.i mentioned this to someone how i could work around this and they said
or alternatively,
The text was updated successfully, but these errors were encountered: