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
I wonder if something like yallop/ocaml-ctypes or LexiFi/gen_js_api would be possible for Melange. "Externalizing" the bindings creation outside the compiler would remove complexity from Melange itself. And from user perspective, it would bring some benefits, like no more need to use [@bs] attributes when defining callbacks in bindings.
Would it be possible? If yes, what kind of primitives should Melange expose for it to happen? Also, what kind of trade-offs would exist? One thing that comes to mind is the zero-cost JS object creation functions exposed by bs.abstract that libraries like reason-reacttake advantage from. Another disadvantage is the fragmentation caused on bindings.
The text was updated successfully, but these errors were encountered:
I wonder if something like yallop/ocaml-ctypes or LexiFi/gen_js_api would be possible for Melange. "Externalizing" the bindings creation outside the compiler would remove complexity from Melange itself. And from user perspective, it would bring some benefits, like no more need to use
[@bs]
attributes when defining callbacks in bindings.Would it be possible? If yes, what kind of primitives should Melange expose for it to happen? Also, what kind of trade-offs would exist? One thing that comes to mind is the zero-cost JS object creation functions exposed by
bs.abstract
that libraries likereason-react
take advantage from. Another disadvantage is the fragmentation caused on bindings.The text was updated successfully, but these errors were encountered: