Thank you for your responses. While I'm convinced that `ParseInLocation` works as intended and I do get that UTC is an unambiguous zone, the only thing I still have problem with is with the way this is phrased in the docs. I had 5 of my colleagues looking at it and none of us has had clarity as to how to interpret these lines:
// First, in the absence of time zone information, Parse interprets a time as UTC;
// ParseInLocation interprets the time as in the given location.
All I'm saying is that it sounds like `Parse` interprets time as UTC in the absence of TZ information, while `ParseInLocation` will interpret it in the given location period (disregarding the TZ if provided).
As the Merriam-Webster reference to the semicolon usage also leaves space for the interpretation the docs should avoid semantically ambiguous lines like those in my opinion. What do you think?
This would be clearer to me (although I've got no idea what style rules, If any are required for the docs):
// First, in the absence of time zone information:
// - Parse interprets a time as UTC
// - ParseInLocation interprets the time as in the given location