On Friday, February 10, 2023 at 7:45:37 PM UTC+1 Ian Lance Taylor wrote: But it's not the case that the timezone abbreviation is never taken into account. As the comment says, the timezone abbreviation is taken into account if it is defined for the current location. For example, if the current location is America/Boise, then MST is meaningful (and so is MDT). if the current location is Europe/Brusselss, then CET is meaningful (and so is CEST among others). This approach is taken because the timezone abbreviations are ambiguous.
I do not yet see where timezone abbreviations are ambiguous... Do you mean there are multiple timezones with the same abbrev? This is certainly not the case for MST... What is the point in taking the timezone into account only if that timezone is in the local timezone? I really wish there would be a way to handle abbreviations exactly the same as numeric offsets as the offset to UTC should be known for the abbreviations, shouldn't they? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/3724f74a-92da-4c4c-bfbc-cc743ad80034n%40googlegroups.com.
