Gregg Reynolds

in the case of digestif, we can define build settings in the package, so e.g. the user can select an implementation by passing one of `--@opam//lib/digestif:c` or `--@opam//lib/digestif:ocaml`. default could...

Another possibility: always use the package name as the namespace prefix. That way both the `ocaml_ns` and the submodules know what the prefix is, so long as they are in...

The main unresolved problem is how to make the compiled ns module available to the submodules, who need it for compilation. We may be able to use the transition function...

There's nothing in the readme about re-graph/destroy, and I don't see any other documentation. I'm using hato.

I was going to say I think this is the correct behavior, insofar as `-no-alias-deps` means exactly "do not look at (into) aliased dependencies." So the aliasing equation in your...

Use case: model the system toolchain (e.g. `/usr/bin/ocamlopt`, `/opt/homebrew/bin/ocamlopt`) for a project that does not use opam. Use case: use custom toolchain that is not in opam.