Hyeseong Kim

Updated the example to 19.0.0-rc.1, and the issue is still there... Updated to 19.0.0 which is the stable release

It's still reproducible, and no fixes are referenced

Updated example to v19.1.0, it's still happening consistently.

Updated examples to React v19.2.0. The issue still exists.

> After this PR, ocaml-lsp-server will be installed in CI (unnecessarily). A common strategy is to separate the dev-only and build-only workflows and run them simultaneously. As I mentioned in...

This is definitely something that needs to be improved, but it's one of the hardest problems. Type inference on polymorphic JSX props is a notorious problem even in the TypeScript...

Doesn't `@meth` work? We also have `@this` binding. Afaik, it works for both regular function and FFI

I've been exploring this for a bit. rescript-schema seems to be a somewhat special case. I believe most apps have a more explicit and idiomatic solution for binding context without...

It seems like there's a lot of `this` dependency, and removing it and going back to the `type t` pattern would require a lot of boilerplate and some breaking changes....

This is definitely a bug, but it makes me think of the constraint. It seems to be not clearly defined.