Thomas Leonard

Are you using some custom collectors? The default ones aren't doing anything that takes any significant time (versions before 0.7 did some GC stats that could be expensive on large...

> I then stumbled upon a new test where dscheck should report an issue but doesn't (I'm not sure if the bug was introduced in this PR, as the test...

OK, here's a simpler test-case that detects the bug with `main` but not with this PR. ```ocaml module Atomic = Dscheck.TracedAtomic let test () = let cancelled = Atomic.make false...

Maybe what I really want is a way to register a C function to be called by `caml_record_signal`. IO libraries like Eio generally have their own ways to wake up...

> I also fear that there would need to be one such fd per domain I don't see why. If fact, we possibly only need one domain to be using...

Good point about signal masks. For most signals (e.g. SIGCHLD) the OCaml handler just triggers an Eio condition and any domains waiting for it will wake up and handle the...

It's up to tls-eio to decide whether closing a TLS flow also closes the underlying flow. For tls-lwt, we have: ```ocaml (** [of_t t] is [ic, oc], the input and...

> I think that the best solution is to require that the underlying flow implements the close operation. Sounds good to me! (it would also be possible to use a...

This seems reasonable to me. Possibly we should have a dedicated `options` argument (extensible variant) as there will likely be loads more special features that could be added (see e.g....

> To avoid having to supply the path to an admin.cap wile, you can make a runner script like /usr/local/bin/ci3-admin The README already suggests setting an alias for this. Some...