Anil Madhavapeddy

That @emillon, promising progress! Would you be able to try building `luv` as a monorepo though; since I think that will still fail as it depends on ctypes. (this feature...

@tsnobip here's an example of a multistage Dockerfile that follows the workflow you describe: https://github.com/ocurrent/ocurrent-deployer/blob/master/Dockerfile The opam deps here are built first, and then the main project in a separate...

To echo @xavierleroy from an opam perspective, this proposal would make the installation of trunk switches for users slightly more complicated, as they would also need to have the right...

@dra27 wrote: > If configure is removed, we wouldn't need a precise version of autoconf (in particular, https://github.com/ocaml/ocaml/pull/11294 would be dropped) I don't see how that follows. The problem in...

Note: I'm told this is a distillation of a real bug found in the Tezos codebase while porting parts of it to use multicore OCaml. (thanks for being early adopters...

Good catch, this looks right to me and I'll test it out later. It would be really useful to craft a test case for this sigaltcase... any ideas on that?

I was thinking more about touching the sigaltstack from the kernel without this patch, which should cause a segfault on OpenBSD. That would then pass with this test and ensure...

Just linking to #11094 which finds a segfault in this area of code

(I think I accidentally rebased @madroach's git commit in my name. That needs a refresh to reflect the original authorship, but the code needs a revision anyway).

This: ``` (imports (https://github.com/ocaml/ocaml 4.08) (https://github.com/ocsigen/lwt 4) (https://github.com/ocaml/re 1)) ``` is sufficient for the duniverse to operate -- I can modify the duniverse tool [metadata](https://github.com/avsm/duniverse/blob/master/src/types.ml#L79) to use this format very...