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.

Sign up for GitHub

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

Jump to bottom

Transpilation approach #1

Closed
echeran opened this issue Feb 27, 2020 · 2 comments · Fixed by #9
Closed

Transpilation approach #1

echeran opened this issue Feb 27, 2020 · 2 comments · Fixed by #9
Assignees
@echeran
Labels
A-ffi Area: FFI, WebAssembly, Transpilation C-meta Component: Relating to ICU4X as a whole T-docs-tests Type: Code change outside core library
Milestone
2020 Q2

Comments

@echeran
Copy link
Contributor

echeran commented Feb 27, 2020

One approach to accomplish the main goals in the OmnICU Charter is to have a transpiler that converts input source code into the equivalent source code for each target language (or platform).

The intent of this approach is to decouple the code deliverable from the target language toolchain and allow the toolchain to optimize code on a per-application basis. The result would allow the target code to run with minimal dependencies and code size.

The input source code should represent the i18n functionality that is in the scope for OmnICU. It should also be able to pass unit tests that check the logical correctness of the input code itself, and do so before any transpilation occurs. This ensures an authoritative source of truth for logical correctness tests, decoupled from target language/runtime effects.
@filmil filmil mentioned this issue Feb 27, 2020
Closed
@sffc
Copy link
Member

sffc commented Apr 16, 2020

Is there anything more about the Transpilation Approach that needs to be documented? If not, please close the issue.

@sffc sffc added the T-docs-tests Type: Code change outside core library label Apr 16, 2020
@sffc sffc linked a pull request Apr 17, 2020 that will close this issue
Add FAQ to Charter on transpiler #9
Merged
@sffc
Copy link
Member

sffc commented Apr 17, 2020

I'm going to close this issue as fixed by #9.

@sffc sffc closed this as completed Apr 17, 2020
@echeran echeran mentioned this issue May 4, 2020
Closed
@sffc sffc added A-ffi Area: FFI, WebAssembly, Transpilation C-meta Component: Relating to ICU4X as a whole labels May 7, 2020
@sffc sffc added this to the 2020 Q2 milestone Jun 17, 2020
@nordzilla nordzilla mentioned this issue Jun 8, 2022
Merged
younies added a commit to younies/icu4x that referenced this issue Jul 31, 2022
@younies
fix comments unicode-org#1.
805d664
younies added a commit to younies/icu4x that referenced this issue Aug 2, 2022
@younies
fix comments unicode-org#1.
a70c9bc
@autarch autarch mentioned this issue Apr 15, 2023
Merged
skius added a commit to skius/icu4x that referenced this issue Aug 31, 2023
@skius
review unicode-org#1
8a0b90c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@echeran echeran

Labels
A-ffi Area: FFI, WebAssembly, Transpilation C-meta Component: Relating to ICU4X as a whole T-docs-tests Type: Code change outside core library
Projects
None yet
Milestone
2020 Q2
Development

Successfully merging a pull request may close this issue.

Add FAQ to Charter on transpiler echeran/icu4x
2 participants
@echeran @sffc