-
Notifications
You must be signed in to change notification settings - Fork 188
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
Make number representations compatible with Wasm #1649
Conversation
4154cf1
to
f2942e4
Compare
f2942e4
to
dd11e23
Compare
9ca2cc0
to
fab177e
Compare
Thanks. Looks good. |
fab177e
to
2b4f30e
Compare
Done. It looks like the failing test will only work if I integrate the single commit from #1650, which redefines This may break programs that do not perform explicit float conversions yet. |
Co-authored-by: Olivier Nicole <olivier@chnik.fr>
2b4f30e
to
256b031
Compare
I removed the last commit, and fixed the hypertree example to use number_t |
Thank you |
This is best reviewed commit by commit. It adds a number of missing conversions, and other changes that have been performed in Wasm_of_ocaml in order to expose number-manipulating functions that are compatible with both the JS and Wasm backends.
This is part of a series of PRs intending to reduce the diff between js_of_ocaml and wasm_of_ocaml.