Jacob Pratt

This is currently possible by going through `Parsed` struct. You would need to parse the format into `Parsed`, alter the year as necessary, and finally convert it to `Date`.

Without even looking into this, I am confident that the multiplication magnifies the inherent error of representing decimal values in floating point numbers. I'm happy to accept your proposed solution...

This has been brought up before, and I'm not aware of how to fix it. My recommendation has always been to use `#[serde(default)]`. If there is a better way, I'm...

Doc improvements are always welcome! It's not a priority for me at the moment.

For panics that are deliberate, it's probably quickest to just check for `assert!` and `.expect` with ripgrep. Any other panics are likely unintentional — I can't think of any edge...

@jeff-hiner I'll be honest, it's not likely to happen. The clippy issue you linked would solve your request while being more general purpose and would avoid the overhead of an...

Note that I was responding to the use of separate feature flags for `Serialize`/`Deserialize` impls, which is not present in `url`. Regardless, `time` also uses a sensible representation for implementing...

> It was claimed, but I don't see any progress over the last year. Are we looking at the same thing? There was an update just a couple days ago...

Things aren't fast in Rust given that it's entirely driven by volunteers. The PR author commented just this week that they intend to continue work on it. Given that you...

Removing the defaults is almost certainly not going to happen. ISO 8601 is at least a possibility, though keeping the non-human-readable compatibility will almost certainly happen. > thus only meaningfully...