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
This feature was removed in #1. While I understand the reason for needing a single type that can dynamically represent different time zones, a project I'm currently working on needs to statically mark a value as being in a specific timezone:
#[derive(Deserialize)]pubstructEvent{pubstart:DateTime<Europe::Berlin>,pubend:DateTime<Europe::Berlin>,// and some irrelevant fields ...}
This is because the timestamps I'm deserializing are not marked with any timezone but the documentation specifies that they are to be interpreted as local times in Germany (and that no DST-ambiguous timestamps occur).
It would be great if this library could support both use-cases.
The text was updated successfully, but these errors were encountered:
This feature was removed in #1. While I understand the reason for needing a single type that can dynamically represent different time zones, a project I'm currently working on needs to statically mark a value as being in a specific timezone:
This is because the timestamps I'm deserializing are not marked with any timezone but the documentation specifies that they are to be interpreted as local times in Germany (and that no DST-ambiguous timestamps occur).
It would be great if this library could support both use-cases.
The text was updated successfully, but these errors were encountered: