Lucas Pluvinage

Two solutions: - short term: in `config.ml` allow devices to extend the generated dune file with arbitrary content (or something specific for ppxs) - long term: let the user write...

Indeed we should install the `.opam.locked` file

I'm interested in seeing progress for this PR. It's relevant for at least two libraries of the OCaml ecosystem: - `meio`: formerly known as `eio-console`, this tool uses the runtime...

> users also want automatically-inferred everything else and where do we stop? Do you have examples of other "automatically-inferred" data that users might request ? For reference, here is how...

One hard thing is automatic caller location. This is currently a hack in my fork of eio.

Because it's using get_callstack it definitely has some runtime overhead. We could also have a global switch for that. Ideally if the compiler generates the location info at the call...

Obviously making the changes will trigger a full rebuild

This page is supposed to provide this feature: https://docs.ci.ocaml.org/package

I can take a look at the solver pool API to make sure it fits what docs CI needed. I remember tweaking from what OCaml-CI does in the solver step.

Instead of propagating voodoo changes directly in the pipeline, it's also possible to require confirmation from an user in the ocurrent interface.