[Issue 17922] SysTime.to
https://issues.dlang.org/show_bug.cgi?id=17922 --- Comment #3 from Jonathan M Davis --- Yeah, unfortunately, there are a number of time zones that don't line up on the hour (usually they then line up on the half hour, but IIRC, not even that is always the case). --
[Issue 17922] SysTime.to
https://issues.dlang.org/show_bug.cgi?id=17922 Uranuz changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Uranuz --- It seems that it was just misunderstanding that it's a minute part in timezone offset. I should post this question at dlang forum first before issuing an error. So there is no problem here. --
[Issue 17922] SysTime.to
https://issues.dlang.org/show_bug.cgi?id=17922 Jonathan M Davis changed: What|Removed |Added CC||issues.dl...@jmdavisprog.co ||m --- Comment #1 from Jonathan M Davis --- So, what's the bug? toISOString does incorrectly put a colon in the timezone, which is bug https://issues.dlang.org/show_bug.cgi?id=15654 But the others are supposed to put a colon there. Were you expecting that there wouldn't be a :00 on the end because you passed a string without it to fromISOExtString? It's not like the SysTime keeps track of how it was created. Or did you expect that the :00 would be stripped off just because it's zeroes? Or is it something else? to*String never strips out zeroes from the time zone if that's what you're looking for. --