-
Notifications
You must be signed in to change notification settings - Fork 48
Derive generic instances for Data.Date.Date and all types in Data.Time #22
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
Conversation
2e54477
to
5391ac1
Compare
I'm not representing a Actually, why not make |
That sounds like a good idea to me! It gets rid of the potential mutability of the date value too then 👍 We'd also need to keep a time offset with it too I think perhaps? That's good too though, as currently the timezone/offset support is Not Good. |
5391ac1
to
d33c20e
Compare
FYI, I'm not using this module anymore (we switched away from PureScript, unfortunately). So if somebody wants to take over this pull request feel free to. |
@garyb what offset/timezone support do you think would be most beneficial? Is it the plan here to incorporate this whole body of (notoriously tricky) offset/timezone logic like a library like moment.js does? Would it be a possibility to merge this PR as it is now and hold off on the move to a newtype around Milliseconds + timezone/offset? Or do you think that's a bad idea? @wereHamster Am I correct in assuming that this PR is pretty complete as is, apart from the possible migration to a newtype around milliseconds + timezone/offset for the Date type? |
@FrigoEU I think it's complete and can be merged. It certainly doesn't break any existing code and generic instance for |
I did notice that there's some Generic Instances missing for Year, DateOfMonth, etc. I could do that work, but tbh I have no idea how to take over a PR :). I agree with the current Generic instance for Date being sound. |
@FrigoEU I think the best way is if I close this one and you open a new one. |
Okido, will do. |
No description provided.