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
Currently we do code generation from Typedtree (OCaml) -> JS source text (x3 variations). It would be easier to do Typedtree -> JS AST (possibly tagged with metadata) -> JS source text (x3 variations).
This would improve the structure of the generation functions.
The text was updated successfully, but these errors were encountered:
Alan's suggestion:
not necessarily the JS AST, but a clean AST where we get rid of the OCaml idiosyncrasies of Typedtree and also include our features such as monadic let bindings as a native feature (instead of through extension points)
Currently we do code generation from Typedtree (OCaml) -> JS source text (x3 variations). It would be easier to do Typedtree -> JS AST (possibly tagged with metadata) -> JS source text (x3 variations).
This would improve the structure of the generation functions.
The text was updated successfully, but these errors were encountered: