rok commented on issue #597: URL: https://github.com/apache/arrow-rs/issues/597#issuecomment-885596294
@velvia > * I actually think if we were to change the underlying timezone data type, it should be a numeric offset, not a string. Strings take up a large amount of space, at least 24 bytes on x86 + the actual storage of the string, and are slow; furthermore every time we need to actually translate it to the offset, which is more likely what we care about for computations. I'd prefer some kind of `TimeOffset` which could simply be `Option<i32>` or something like that - that's only 5 bytes. :) Offsets are much more practical indeed but don't cover things like daylight savings changes and human readable timezones (e.g. EST, PST, CET). But I don't know what your scope is and offsets might be enough. [Chrono-tz](https://github.com/chronotope/chrono-tz/) seems to implement a timezone database in case you decide to look into that direction. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
