Skip to content

fix a bug in Js_fn module #263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 18, 2016
Merged

fix a bug in Js_fn module #263

merged 1 commit into from
Apr 18, 2016

Conversation

bobzhang
Copy link
Member

@bobzhang bobzhang commented Apr 18, 2016

TODO: we need make Js_fn.mk0 a little nice, the hack that remove unused single parameter seems to be unnecessary any more

@bobzhang bobzhang merged commit c95e570 into master Apr 18, 2016
@bobzhang bobzhang deleted the event_ffi branch April 18, 2016 14:34
kevinbarabash pushed a commit to kevinbarabash/rescript-compiler that referenced this pull request Dec 24, 2021
Fixes rescript-lang#277
Fixes rescript-lang#263

Now that rescript-lang#4967 has landed:
- Parse `{"foo": int}` as ocaml `{. foo: int}`. Previously it parsed into ocaml `{. foo: int} Js.t`
- Remove a tiny printing optimizations for `Js.t`.
- For React's PPX 3, generate objects directly instead of `Js.t` objects. cc @rickyvetter @ryyppy for ppx4.
- The re->res converter automatically removes the `Js.t` part.
- Said converter has a bug (rescript-lang#263) that converts `Js.t({..}) as 'a` into `{..} as 'a` from naturally forgetting to special-case that path. Now this bug is conveniently ~~made into a feature~~ obsolete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant