yes
I'm looking for an efficient way to calculate the difference in milliseconds between two dates I have as strings. Currently I'm using chrono and doing something like this: https://gist.github.com/endor/09339daf97ea33418ab69492d8f2cb75. Is there a more efficient way?
I tried them yes. With just some basic Instant::now,elapsed()/println! I think the difference was ~1000ns or so, if I remember correctly. I think there would be some performance improvement if I could instantiate a DateTime without all the checks. Not sure how to do that and if that would actually save a lot of time.
Basically the cleint will have the timezones in their requests and I will convert them using the timezone they provided, is this achievable with the chrono library?
I was thinking using fixed offset
then converting it somehow into UTC but can’t find how
looking for the docs
if you parse it into a datetime
mydt you should be able to do mydt.with_timezone(Utc) https://docs.rs/chrono/0.4.6/chrono/struct.DateTime.html#method.with_timezone
thanks
let pacific_time = Pacific.from_local_datetime(&dbg!(date.and_hms(dbg!(hour), 0, 0))).unwrap();
oh, daylight saving
I thought it starts second week of march?
Okay I see that rule only applies after 2005
specifically that time
I'm glad it works for you!
nevermind
is there only one ambigous result for the whole year?
because when transitioning to daylight it just skips an hour
while transitioning back to standard will yeild two hours which is where ambiguity comes in
actually, sometimes governments decide to just change the time, which would also cause that. It doesn't happen much, though
let tz: Tz = dbg!(timezone.parse().map_err(|e| format!("{}", e)))?;
let local = match dbg!(tz.from_local_datetime(dbg!(date))) {[src/actors/date_converter.rs:16] timezone.parse().map_err(|e| format!("{}" , e)) = Ok(
America/Los_Angeles
)
[src/actors/date_converter.rs:17] date = 2019-04-10T02:59:00
[src/actors/date_converter.rs:17] tz.from_local_datetime(dbg!(date)) = Single(
2019-04-10T02:59:00PDT
)
the time
2019-04-10T02:59:00 does not exist in PDT, however it is returning a result
if I provide
2019-04-10Y02:01:00 instead, it does the correct thing and return none: [src/actors/date_converter.rs:16] timezone.parse().map_err(|e| format!("{}" , e)) = Ok(
America/Los_Angeles
)
[src/actors/date_converter.rs:17] date = 2019-03-10T02:01:00
[src/actors/date_converter.rs:17] tz.from_local_datetime(dbg!(date)) = None
here are two side by side, with one of them a minute before the other
[src/actors/date_converter.rs:16] timezone.parse().map_err(|e| format!("{}" , e)) = Ok(
America/Los_Angeles
)
[src/actors/date_converter.rs:17] date = 2019-03-10T02:58:00
[src/actors/date_converter.rs:17] tz.from_local_datetime(dbg!(date)) = None
[src/actors/date_converter.rs:16] timezone.parse().map_err(|e| format!("{}" , e)) = Ok(
America/Los_Angeles
)
[src/actors/date_converter.rs:17] date = 2019-04-10T02:59:00
[src/actors/date_converter.rs:17] tz.from_local_datetime(dbg!(date)) = Single(
2019-04-10T02:59:00PDT
)
or, wrong
try
ts_microseconds