Hyeseong Kim

That's what exactly we have already. Just need to expose it to the API surface

Ah yes, this currently has to be readjusted every time we change the output. The gentype test suite is not very sufficient. IMHO eventually gentype would be ported into the...

sure. I will try that

Oh, sorry. I will look into it in a few hours

Thank you @illusionalsagacity After cleaning things up, I'll release a new release.

Good catch. I think it's an issue of the [Core](https://github.com/rescript-association/rescript-core) binding It actually need runtime to handle nested option correctly ```res module Map = { include Map let get =...

We might have the opportunity to explore an alternative syntax. e.g. https://github.com/tc39/proposal-explicit-resource-management

Well, I'm not a fan of exposing a bloated API surface upfront by providing bindings. Some should strictly follow the binding style, but users should easily add or extend simple...

If you use it in your project and you want to upstream it. I will merge unless there is a style conflict. Otherwise we can open issue and discuss first

You're right. The current behavior of the functors is not ideal. We need to provide more options to perform DCE and choose whether to inline or not.