zapashcanon 11 months ago
parent
commit
7c08726986
Signed by: zapashcanon GPG Key ID: 8981C3C62D1D28F1
  1. 15
      bib.bib
  2. 8
      wasocaml.tex

15
bib.bib

@ -126,6 +126,20 @@
year={2022}
}
@misc{Sha22,
title={{WebAssembly backend merged into GHC}},
author={Shao, Cheng},
year={2022},
howpublished = "\url{https://www.tweag.io/blog/2022-11-22-wasm-backend-merged-in-ghc}"
}
@software{The22,
title={{dart2wasm}},
author={{The Dart Project Authors}},
year={2022},
url={https://github.com/dart-lang/sdk/tree/main/pkg/dart2wasm}
}
@software{Web22,
title={{Reference-Typed Strings Proposal for WebAssembly}},
author={{WebAssembly Community Group participants}},
@ -133,6 +147,7 @@
year={2022}
}
@misc{AC23,
title={{OCaml on WasmGC}},
author={Andrès, Léo and Chambart, Pierre},

8
wasocaml.tex

@ -592,11 +592,11 @@ It might be a temporary solution.
\paragraph{Go.}
\paragraph{Haskell.}
\paragraph{Haskell.} ~\cite{Sha22}
\subsubsection{Targeting Wasm-GC}
\paragraph{Dart.}
\paragraph{Dart.} ~\cite{The22}
\paragraph{Scheme.}
@ -672,6 +672,10 @@ For this reason, we cannot expect it them be widely available soon.
On the other hand, it means that our compiler will be ready when
browsers start deploying new Wasm extensions.
Our future plans are to complete the Wasm implementations of OCaml externals, to implement the various FFI
mechanisms, support effect handlers and to move Wasocaml to Flambda2. All of these would allow to easily
deploy multi-language software easily on the browser while having good and predictable performances.
% TODO:
% For the conclusion, I really want to hear about lessons learned, moving forward, etc. Especially since there's no practical use for this work at this time, why should the broader OCaml community be interested in it? Is there something unique that OCaml offers wasm? Are there lessons that we--the OCaml community of developers--can learn from your experience? Were there specific limitations of OCaml that we should be aware of and work on? Are specific strengths of OCaml that distinguish your effort from those working in other languages and ecosystems? For the conclusion, I really want to hear about lessons learned, moving forward, etc. Especially since there's no practical use for this work at this time, why should the broader OCaml community be interested in it? Is there something unique that OCaml offers wasm? Are there lessons that we--the OCaml community of developers--can learn from your experience? Were there specific limitations of OCaml that we should be aware of and work on? Are specific strengths of OCaml that distinguish your effort from those working in other languages and ecosystems?

Loading…
Cancel
Save