-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Date & Time #19
Comments
cc @CosmicHorrorDev. BTW, if you haven't already, I'd suggest subscribing to all activity on this repo since you said you intend to help develop and maintain it. :) |
I would personally just depend on |
Good point. |
It's not a |
Ah I didn't realize 😅 It looks like it only needs |
Yeah, I asked the maintainer in a PM if he'd be interested in a PR for that. Unlikely that he's not but you never know. :) |
He says, he's good with that. 👍 So please go ahead. |
One issue though: Btw, Ed said to add |
Ah yeah that's a good point 😿 Whelp then I think we carry on with copying out the parts we need |
Yeah. 🤷 Still if we try and keep modifications to minimum, we can ditch our copy once toml_edit can bump its MSRV to 1.81. |
This should have been supported from the day 1. I think we need to take the user-facing API from
toml_datetime
(so we don't need to depend on another external crate) and perhaps also take the parsing code fromtoml_edit
(with some adaptation of course).I think this will also fix a bunch of failing cases in the from the test harness (#11).
The text was updated successfully, but these errors were encountered: