Skip to content
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

Closed
1 of 2 tasks
CoffeeFlux opened this issue Feb 4, 2021 · 6 comments
Closed
1 of 2 tasks

Experiment with icu4x usage for wasm #47875

CoffeeFlux opened this issue Feb 4, 2021 · 6 comments
Assignees
Labels
arch-wasm WebAssembly architecture area-System.Globalization size-reduction Issues impacting final app size primary for size sensitive workloads
Milestone

Comments

@CoffeeFlux
Copy link
Contributor

CoffeeFlux commented Feb 4, 2021

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:

  • Identify whether the ICU APIs we call right now are implemented in icu4x or what the gap is (list of functions we use here)
  • Call into a Rust library from Mono wasm

Also of note: icu4x is not targeting full no_std compatibility for now, see unicode-org/icu4x#77

@CoffeeFlux CoffeeFlux added area-System.Globalization size-reduction Issues impacting final app size primary for size sensitive workloads labels Feb 4, 2021
@ghost
Copy link

ghost commented Feb 4, 2021

Tagging subscribers to this area: @tarekgh, @safern, @krwq
See info in area-owners.md if you want to be subscribed.

Issue Details

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:

  • Identify the ICU APIs we call right now and ensure they're implemented in icu4x (or open issues as appropriate)
  • Try to call into a Rust library from Mono wasm (should be possible, but nontrivial)
Author: CoffeeFlux
Assignees: -
Labels:

area-System.Globalization, size-reduction

Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 4, 2021
@CoffeeFlux CoffeeFlux removed the untriaged New issue has not been triaged by the area owner label Feb 4, 2021
@CoffeeFlux CoffeeFlux added this to the Future milestone Feb 4, 2021
@tarekgh tarekgh added the arch-wasm WebAssembly architecture label Feb 4, 2021
@ghost
Copy link

ghost commented Feb 4, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

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:

  • Identify the ICU APIs we call right now and ensure they're implemented in icu4x (or open issues as appropriate)
  • Try to call into a Rust library from Mono wasm (should be possible, but nontrivial)

Also of note: icu4x is not targeting full no_std compatibility for now, see unicode-org/icu4x#77

Author: CoffeeFlux
Assignees: -
Labels:

arch-wasm, area-System.Globalization, size-reduction

Milestone: Future

@lambdageek
Copy link
Member

Since unicode-org/icu4x#911 icu4x builds with no_std. Also they recently hit 1.0.0-beta1 https://crates.io/crates/icu/1.0.0-beta1

It's worth revisiting this

@lambdageek lambdageek modified the milestones: Future, 8.0.0 Aug 5, 2022
@tarekgh
Copy link
Member

tarekgh commented Aug 5, 2022

@lambdageek yes, it is worth trying in the next cycle.

@naricc naricc self-assigned this Sep 26, 2022
@naricc
Copy link
Contributor

naricc commented Sep 26, 2022

I plan to take a look at this in the November time frame.

@SamMonoRT
Copy link
Member

We are going to consider this as a future project. Closing this issue.

@ghost ghost locked as resolved and limited conversation to collaborators May 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Globalization size-reduction Issues impacting final app size primary for size sensitive workloads
Projects
None yet
Development

No branches or pull requests

5 participants