Henri Sivonen

Oh, and let's surface the only comment I put in the code: Do we want to support TLDs with MX records or require at least one more level in the...

> I looked a bit more at not using the host parser: > > * We end up passing _beStrict_ is true (aside: we'd have to make this a named...

AFAICT, an underscore in the domain part currently results in `.validity` reporting `typeMismatch: true` in Firefox, Safari, and Chrome. As far as I'm aware, this isn't a source of complaints,...

> @hsivonen asked: > > > @aphillips , What's the purpose of hosting "." out of utext when localpart is defined as in the PR? AFAICT, the ABNF would mean...

> Wouldn't treating `h24` as an alias reinforce the exact reason for the initial change Henri proposed? Yes, but it might still probably be better to accept `h24` as an...

> What would happen if a locale changed to a 24 hour system and the value is aliased? Oops, I failed to add my reply to this point: This is...

> So, the question is: what is the correct behavior here? Should dates in Gregorian-derived calendars such as buddhist and japanese also override the cutover to match ECMAScript's Gregorian behavior?...

> Is this in the spec somewhere? * ISO is proleptic. * The era reference points for `gregorian` in [`supplementalData.xml`](https://github.com/unicode-org/cldr/blob/main/common/supplemental/supplementalData.xml) are true only if `gregorian` means _proleptic_ Gregorian. (It sure...

> `utf8_iter` can be removed at 1.79 MSRV because it gets added to the standard library: https://doc.rust-lang.org/std/primitive.slice.html#method.utf8_chunks That's not the same thing. utf8_iter provides an API that's so close to...

Making UTF-16 support optional makes not only utf16_iter optional but also write16.