-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experiment with icu4x usage for wasm #47875
Comments
Tagging subscribers to this area: @tarekgh, @safern, @krwq Issue Detailsicu4x is an ICU implementation targeting WebAssembly that is intended to be modular and flexible. There is a chance that it could offer size or performance benefits over icu4c, and as the library matures experimenting with using it could be valuable. Before attempting to implement this in full, we would need to:
|
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsicu4x is an ICU implementation targeting WebAssembly that is intended to be modular and flexible. There is a chance that it could offer size or performance benefits over icu4c, and as the library matures experimenting with using it could be valuable. Before attempting to implement this in full, we would need to:
Also of note: icu4x is not targeting full
|
Since unicode-org/icu4x#911 icu4x builds with It's worth revisiting this |
@lambdageek yes, it is worth trying in the next cycle. |
I plan to take a look at this in the November time frame. |
We are going to consider this as a future project. Closing this issue. |
icu4x is an ICU implementation targeting WebAssembly that is intended to be modular and flexible. There is a chance that it could offer size or performance benefits over icu4c, and as the library matures experimenting with using it could be valuable.
Before attempting to implement this in full, we would need to:
Also of note: icu4x is not targeting full
no_std
compatibility for now, see unicode-org/icu4x#77The text was updated successfully, but these errors were encountered: