Robert Bastian

This is actually way more complex: https://unicode.org/reports/tr35/tr35-dates.html#Contents:~:text=Otherwise%20do%20the,Pacific%20Time%20(Whitehorse)%22

Bad news is that it also depends on the locale's region.

I'd prefer 3 or 2. I think we should get rid of all the markers, so there's probably not much of an advantage of 2.

I don't think the list of use cases sounds correct. I think it gets too hung up on IANA IDs, when all they are are a way to identify a...

> Mitigate the risk by removing canonicalization behavior from APIs, so that ECMAScript will never replace user-inputted IDs with a canonical ID. If a user provides Europe/Kiev or Europe/Kyiv to...

We had an extensive discussion about the meaning of "canonical" this morning, and this the API and guarantees we are converging on: ```rust impl IanaParser { /// Parses an IANA...

> Instead of a strongly-opinionated warning about using normalization, I think it'd be better to explain the two operations and what would be the reasons to use one or the...

is this still targeted for v48?

Doubly nested Results are required in case the `fmt::Write` is infallible, such as `String`. The outer `Result` can then be unwrapped and the error case cleanly disappears.

That's not what I'm trying to get at. `TryWriteable::write_to_string` returns `Result`, and `Self::Error` does not need to contain a `core::fmt::Error` variant (it shouldn't because that's unreachable). If `try_write_to` returned an...