Shane F. Carr
Shane F. Carr
It's not clear to me that MF is the _right place_ to do the "float/unfloat". If the time zone is hard-coded in the message, how do you know how to...
I don't think we've addressed this comment: > It's not clear to me that MF is the _right place_ to do the "float/unfloat". If the time zone is hard-coded in...
+1 on making IANA zone and BCP-47 zone differently named options if we support both.
Given that the `timeZone` option is clearly marked as "Proposed", I think this need not block LDML 47
Yeah, the AO should reference BCP-47 calendar IDs, not TR 35 calendar IDs, which are different (for example, "gregory" instead of "gregorian") ``` Intl.supportedValuesOf("calendar") (18) ['buddhist', 'chinese', 'coptic', 'dangi', 'ethioaa',...
list/and@1 also showed up, but I didn't take the time to copy it into the table; I tried to include a representative cross-section in the OP. "baked size" refers to...
Note: I have some measurements in https://github.com/unicode-org/icu4x/issues/1317#issuecomment-2330283151 that illustrate the two types of binary size consumed by the baked data: the strings themselves (`borrows_size`) and the struct stacks (`size_of`).
> I don't see any reason for us to diverge from this by default. Ok We could explore `DataLoad` or `DataProvide`, but if `DataProvider` is conformant with the Rust RFC,...
This is a sub-point on Reason 2, but it might deserve being its own reason: I honestly find camel case hard to read. I squint at my screen to figure...
On trait names: I generally strongly prefer general solutions that avoid clashes ("just work"), but we can fall back to a case-by-case bikeshed given that the referenced Rust RFC is...