Raphaël Proust

Do we need to `#include` an additional file for windows on 5.2? The CI has the following error for that specific combination: ``` #=== ERROR while compiling lwt.dev ============================================# #...

@BraulioVM I think the addition would make sense. Note that I would want to keep backwards compatibility. So it can't be a change in the existing `pread` function. I'd suggest...

Note that if backspace returns to normal mode, then `/?` also changes the direction. It does so by switching modes repeatedly though. Whilst I like the command window being a...

FWIW, the inconsistencies in ocaml version support is the reason why we moved `lwt_domain` out of the main repo and into its own: https://github.com/ocsigen/lwt_domain. I haven't yet removed the package...

The CI failure for the doc seems to be that `lwt_sequence` is deprecated… is there a way to exclude this module from the doc? I don't know of a way...

bash should, and bash would, but macos ships a bash version that is dated, as in a version that is nearly old enough to drink. Apparently that old version of...

The lower-bounds on the `menhir` dependency constraint seem too lose. After downgrading ``` The following actions will be performed: === remove 4 packages - remove menhirCST 20231231 [conflicts with dune]...

I (being an opam-repository maintainer but voicing my own personal opinion) think that this additional opam-repository is a good idea. I'm not convinced it'll take pressure off of the `ocaml/opam-repository`...

`get_backtrace` has the following caveat > If the call is not inside an exception handler, the returned backtrace is unspecified. In the motivating example, the code is not "inside an...

So it seems `reraise` is maybe less useful than I originally thought. In practice it seems to work in Lwt to use `reraise` in catch-all branches. I guess it's brittle...