Gabriel Scherer

To summarize my reasoning on the upstream issue https://github.com/ocaml/ocaml/issues/12636 : - I believe that something goes wrong on new OSX versions when combining OCaml threads and `fork()`. - I don't...

Regarding an ocaml-lsp workaround: I think that it would be easier to look at the usage context for `spawn` inside ocaml-lsp. The one instance I found (hopefully the only one?)...

(But yes it would be even easier to reuse other people's work to fix similar issues. It seems unfortunate that dune's improvement to the `spawn` library are currently only available...

Thanks! I am very bad at releasing stuff, so I never got the courage to do it myself, but having a release is nice. (I vaguely remember that I promised...

My understanding is that the current plan to fix this problem is described in https://github.com/ocaml/ocaml/issues/11589 , and that @damiendoligez and @stedolan are currently working on it at some non-zero average...

> (Note: as pointed out to me by Denis Merigoux, it would be nice to have a library in OCaml to print such nice error messages, in the style of...

Thanks for the ping! The increase in feature scope had somehow suspended this PR from my memory. I integrated @garrigue's review comments, and I worked out a fix for the...

This still needs an approval before we can merge.

By "the reverse way", do you mean that if the lookup chains finds first D1 and then D2, and in fact D2 double-underscore-simplifies into D1, you would rather keep D2...

We are talking about two successive aliases that would become `module M = ` and `module M = ` in the expansion trace. If `path` and `new_path` (which is an...