Shane F. Carr

> Why not make it a host hook if they are meant to be equal? They aren't equal. For example, I set my Accept-Language to `['eu', 'en-US']`, but my DefaultLocale...

The anchor era should be the one with the same name as the calendar, which is the one starting in 0008 CE

2024-03-28 TG2 notes: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-03-28.md#clarification-on-partitiondatetimepattern-constructing-numberformat-instances

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-05-04.md#add-properties-of-intllocale-instances-section

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-12-08.md#add-support-for-more-subtags-580 Conclusion: Move forward with adding more locale keywords. Add any that are in UTS 35 that impact ECMA-402 formatters, no more, no less.

Looking over the table in UTS 35: https://www.unicode.org/reports/tr35/tr35.html#Key_Type_Definitions It seems that there are 3 keywords that might be relevant (besides rg and sd): - `-u-fw` but only for the Intl...

This is blocked on `-u-ss` and `-u-dx` being implemented in both ICU4X and ICU4C.

I'm going to close this; @jugglinmike please make an issue with follow-up work.

Returning strings "just works" in backends that support returning allocated strings (i.e. C++ but not C). https://github.com/rust-diplomat/diplomat/blob/main/example/src/fixed_decimal.rs#L23 ```rust #[diplomat::rust_link(fixed_decimal::FixedDecimal::write_to, FnInStruct)] pub fn to_string(&self, to: &mut DiplomatWriteable) -> Result { ```...

Number includes these types only because they are required for IEEE floating point compliance. They should not be added to BigDecimal in my opinion.