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
ReScript 11 introduces a new "uncurried" mode, enabled by default. This mode is fundamentally incompatible with the -bs (soon to be -mel) generated output. I have forked the runtime and would like to support both curried and uncurried mode as not everyone can migrate quickly. Converting the runtime wasn't too hard, but I had to abandon the effort when I realised the atdgen output makes use of curried functions (which is totally normal in OCaml code).
Fixing this requires adding a new generated code path for ReScript. If developed hand-in-hand with a new runtime architecture it might be a good opportunity to make use of ReScript-specific features.
Continuing the discussion I started in #375 (comment)
ReScript 11 introduces a new "uncurried" mode, enabled by default. This mode is fundamentally incompatible with the
-bs
(soon to be-mel
) generated output. I have forked the runtime and would like to support both curried and uncurried mode as not everyone can migrate quickly. Converting the runtime wasn't too hard, but I had to abandon the effort when I realised theatdgen
output makes use of curried functions (which is totally normal in OCaml code).Fixing this requires adding a new generated code path for ReScript. If developed hand-in-hand with a new runtime architecture it might be a good opportunity to make use of ReScript-specific features.
Related: #324
The text was updated successfully, but these errors were encountered: