Shane F. Carr
Shane F. Carr
More TG2 discussion: https://github.com/tc39/ecma402/blob/main/meetings/notes-2025-09-11.md#editorial-simplify-numberformat-978
We've agreed on a path forward that improves this PR. @gibson042 intends to push a fix.
Are you aware of [ICU4X](https://github.com/unicode-org/icu4x), which we've built from the ground up to work well with WebAssembly? It is no_std so doesn't even need WASI in order to build.
> Thanks @sffc for your feedback > > > Are you aware of [ICU4X](https://github.com/unicode-org/icu4x), which we've built from the ground up to work well with WebAssembly? It is no_std so...
This seems straightforward and it can help prevent errors when merging proposals, implementing the spec, etc. It should be done in a quiet time when there are not other big...
TG2 discussion: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-11-25.md#normative-add-8-new-numbering-systems-for-unicode-16-929
TG2 approval: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-12-19.md#normative-add-8-new-numbering-systems-for-unicode-16-929
Duplicate of https://github.com/tc39/proposal-intl-duration-format/issues/65, I think.
It is a valid use case that is not supported right now. I'm okay punting this to DurationFormat v2, unless it requires breaking something we've done in v1. @ryzokuken Can...
Discussion 2021-01-13: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-01-13.md#how-to-format-050-days-025-hours-or-325-minutes-89 Conclusion: @ryzokuken to come up with a spec text modification to demonstrate this possibility, but we will not put it into the current proposal.