commit 02876466e78d9e4dcaa738d24c7a64b93562c8c2 parent f0fc0fd091dbb15baf4847983917bec1bec200dd Author: Byron Torres <b@torresjrjr.com> Date: Sat, 29 Jan 2022 19:07:06 +0000 rm comment on returning timezone pointers Signed-off-by: Byron Torres <b@torresjrjr.com> Diffstat:
| M | time/olson/olson.ha | | | 10 | ++-------- |
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/time/olson/olson.ha b/time/olson/olson.ha @@ -16,17 +16,11 @@ export type invalidtzif = !void; // Olson timezones default to using the [[chrono::UTC]] timescale and // [[chrono::EARTH_DAY]] daylength. // -// TODO: tidy up errors? -// TODO: return locality instead? see below. +// TODO: Tidy up errors. +// export fn tz(name: str) (chrono::timezone | errors::overflow | fs::error | io::error | invalidtzif) = { switch (name) { case "Local" => - // returning a timezone instead of a locality (pointer to - // timezone) avoids hidden allocation, but if we decide that - // chrono::local might change during the lifetime of a long - // running program (say, some daemon which is smart enough to - // update it's zones as time months go by), we lose this - // ability. return *chrono::local; case "UTC" => return *chrono::UTC_Z;