Florian Angeletti

It is the bytecode side of `Dynlink` that pulls part of the compiler bytecode library (in particular `Symtable`) as a dependency. On the native side, it only uses `Cmxs_format`, `Cmi_format`...

@dra27: If I am not mistaken, the exceptions can only be raised by OCaml code that links Effect, thus it seems fine to do the initialization only when linking the...

I think that renaming the exception to `Effect.Unhandled` is definitively a good idea. Thinking a bit about the `Effect` module, I was wondering about the long term expectation for this...

Concerning the less detailed printer, this can be solved by using the same `Obj` printer than `Printexc`, isn't it? I have the impression that if we register the `Unhandled` exception...

Here is an implementation of my proposal to move the exception printer inside the `Effect` module: https://github.com/Octachron/ocaml/commit/78f2d2ae7007d1ed11ffdba1970d34c720652edb .

@kayceesrk , gentle ping: if possible I would prefer to have this change in the first beta. Do you have any opinions on the commit that @xavierleroy and me are...

I have updated and rebased the PR and added @xavierleroy's commit and mine to the branch. I have also renamed the `Continuation_already_taken` exception to `Continuation_already_resumed` to align the exception name...

I have pushed a commit that transforms the remaining TODO comments into a latex comment (with @kayceesrk approval). I will squash and merge the PR once the CI returns greens.

I still think that it would be a good idea to spend some time to expand the API exposed by the toplevel compiler library.

Yes, a new port should be moved to the next version at this point of the release. We could possibly discuss adding it to the possible midpoint `5.0.1` release.