js_of_ocaml
js_of_ocaml copied to clipboard
ocsigen
ES6 Support
No real use case for the moment but as lots of popular JavaScript frameworks switch to ES6 (like React and ReactNative), it would be great to have ES6 support. I would like to begin a binding to ReactNative and use the ES6 interface is easier.
One way would be to rely on some external javascript parser (https://github.com/facebook/flow ?)
How are WeakSet and WeakMap related to this issue ? My understanding is that one can already use them to write bindings.
I'm fact, they are already used in the jsoo runtime. See https://github.com/ocsigen/js_of_ocaml/blob/09d5731241917577e9c16b6a0063c23baae00df8/runtime/marshal.js#L435
Ah, I had thought the reason js_of_ocaml didn't support Weak was just because JavaScript doesn't support any form of weak references, but maybe I'm just wrong. Maybe it's just that either (1) things were different in the past or (2) WeakMap/WeakSet are somehow not sufficiently powerful.
Indeed, the ocaml weak reference semantic cannot be implemented using weak map / weak set
Oh, I see, WeakMap and WeakSet are not what I expected them to be. Their keys are weak!
I have now also learned about WeakRef, but it looks like browser support is still quite limited.
It might be worth revisiting this in 2021.
Because the output uses Common JS, it can be difficult to integrate with existing projects that use modern, ES6 style JavaScript. ES6 would also allow the JS to work client-side or server-side by default, since browsers now have broad ES6 support.
One could try to port new js feature implemented in https://github.com/returntocorp/pfff/blob/develop/lang_js/parsing/parser_js.mly
Oh, I see, WeakMap and WeakSet are not what I expected them to be. Their keys are weak!
I have now also learned about WeakRef, but it looks like browser support is still quite limited.
WeakRef are now used to implement the ocaml weak semantic.