Curtis Vogt

I would say just go for it and don't worry about how breaking the change is to start with. We need a prototype that demonstrates a performance improvement over the...

I've been doing some experimentation around having `FixedTimeZone` without the name field and the results are promising so far. The design is rather rough so far but I'll continue to...

TimeZones doesn't spawn Julia processes during the build so that part is unrelated (probably spawned by Pkg). There are some parts of the build where memory could be reduced but...

At the moment equality between `FixedTimeZone`s compares the name, standard time offset, and daylight saving time offset. ```julia julia> x = FixedTimeZone("", 3600) UTC+01:00 julia> y = tz"UTC+01:00" UTC+01:00 julia>...

> The "instead of in local time" clause implied to me that when `from_utc=false` the `DateTime` would be _converted_ from `localzone()` into the specified `TimeZone`, but that is not the...

You can use access the offset of a specific `ZonedDateTime` via: ```julia julia> using TimeZones julia> now(tz"America/New_York").zone.offset UTC-5/+1 julia> string(ans) "-04:00" ``` If this is something you're just wanting to...

I'll note that it is not just leading zeroes as `"2000-1-1T0:0:0.0-1:2"` will also fail. This seems to be a rather unusual time zone format to be parsing. Can you provide...

The default would have to be user specified otherwise people could be very surprised when we assume the local time zone or UTC.

I think this a keyword could be added to specify the `DateFormat` does not contain a time zone. Asides: - You should really use `dateformat"yyyy-mm-dd HH:MM"` if you want performant...

Unfortunately no updates at this time. PRs are welcome. I do still recommend using `parse` to make your intent clear. The constructor is around and probably will continue to be...