Eduardo Rafael

The main benefit that I see is having the wrapper, currently camlzip fails to build with zlib.

@xavierleroy module name conflict, camlzip has a module called zlib, zlib is a library called zlib, so it will fail at link time because camlzip is not wrapped. Of course...

Will be looking on this soon

At least for OCaml the issue was that it was accessing `process.env` right after load and not every time the LSP was executed. This fixes that https://github.com/ocamllabs/vscode-ocaml-platform/pull/1322/files

@NathanReb is code unload part of the current JIT implementation?

@mshinwell if you have time, please share, I'm interested on it for Tezos and I got an example working but only if the code has no data reference(I can ensure...

I was actually in process of implementing support for the complete `Env.t` on the `cmt` to do `Typedtree -> Lambda` after the fact without IO. So this for me is...

Yeah I did the same yesterday, seems like storing the coercion is the best idea as it is a simple structure, overall I think it will not be a significant...

This may be a really niche property, but because of this any PPX that is used through `staged_pps` on Dune, will be able to be executed only once instead of...

I would also like to have it using dune + autoconf, like opam itself does it. It simplifies a lot when cross compiling zarith to other platforms.