You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be cool to be able to run an OCaml toplevel or Coq in a browser.
Directly loading wasma/wasmo files should be easy. Maybe we want to provide a way to turn them into a directory containing the Wasm code and a source map?
Dynlink for cmo / cma files would require more work. One need to embed some bytecode metadata. The linking convention might be a different as well (going through an array of global data).
Js_of_ocaml provides a virtual filesystem that can contain the libraries and the cmi files. We probably want to implement this functionality as well. Alternatively, with the JSPI API, it should be possible to load these files asynchronously from the Web server.
Finally, to compile cmo files we will need to embed wasm_of_ocaml. But we probably do not want to embed Binaryen as well. So we probably want to generate Wasm binary modules directly (see #90).
The text was updated successfully, but these errors were encountered:
It would be cool to be able to run an OCaml toplevel or Coq in a browser.
Directly loading wasma/wasmo files should be easy. Maybe we want to provide a way to turn them into a directory containing the Wasm code and a source map?
Dynlink for cmo / cma files would require more work. One need to embed some bytecode metadata. The linking convention might be a different as well (going through an array of global data).
Js_of_ocaml provides a virtual filesystem that can contain the libraries and the cmi files. We probably want to implement this functionality as well. Alternatively, with the JSPI API, it should be possible to load these files asynchronously from the Web server.
Finally, to compile cmo files we will need to embed wasm_of_ocaml. But we probably do not want to embed Binaryen as well. So we probably want to generate Wasm binary modules directly (see #90).
The text was updated successfully, but these errors were encountered: