You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to parse the date/time "Sun, 28 Apr 2024 11:05:00 GMT" with "%a, %d %b %Y %H:%M:%S %Z" it claims that there is not enough information. Is there something wrong with my format or understanding of the process?
Thanks for the links.
It looks like the issue is that it can be ambiguous, the timezone abbreviation. What are your thoughts on implementing the common timezones and producing a helpful error like "timezone not implemented"?
What are your thoughts on implementing the common timezones and producing a helpful error like "timezone not implemented"?
It is on my wishlist 😄. We would need to come up with some criteria for inclusion. Two criteria I think are reasonable is that the abbreviation should be used in the IANA time zone database and that it should be in use currently (not historical). Then the subjective part of what is common... but that may turn out not be too difficult to come up with.
When trying to parse the date/time
"Sun, 28 Apr 2024 11:05:00 GMT"
with"%a, %d %b %Y %H:%M:%S %Z"
it claims that there is not enough information. Is there something wrong with my format or understanding of the process?Rust playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=fa3d8c9d12107f73fa2eff695f98ab9e
The text was updated successfully, but these errors were encountered: