Leo White

> Leo seems to be advocating explicit use of the ret type, that is, an explicit encoding of shallow handlers into deep handlers. That is a reasonable description of what...

> continue with comes from the internal implementation approach for shallow handlers in Multicore OCaml Note that `continue ... with ...` is a more efficient primitive than just `continue` and...

Surely: ```ocaml let decr = function | (0:int None | (n:int Some (n-1) ``` IIRC @trefis once looked at implementing this.

I think we should avoid mentioning `.cmi` files. The error message is meant for consumption by the programmer, and the programmer does not know what a `.cmi` file is: the...

I think that your proposal doesn't clash with anything. But I'd probably still try for `"foo"u` and `'a'u` for consistency with number literals and other languages even though they can...

I'd just like to register my disagreement with Vincent. The dependency on compiler-libs has always been a huge pain, and seems entirely unnecessary. I strongly support this PR.

Can we just press merge now, or is there something else we are waiting for?

> bin-doc reads the .cmt file, extracts the doc info, and stores it in a new (?) cmd format. It actually reads the `.ml(i)` file to extract the doc info....

> discuss interaction with module inclusion relation I think that the best way to think of these is as a set of module paths. This means signature inclusion can just...

It's perhaps worth discussing here a slightly larger change that I think would be a huge improvement: store the current level as part of the environment. Then instead of `with_`...