Gabriel Scherer

The reproduction case does not seem to use any marshalling, so the relation if it exists would be fairly subtle -- maybe it is due to simliar pacing issues, but...

I would be happy to approve and merge this PR if the recommendations of Xavier are implemented: > * The target systems we care about are 64-bit architecture with alignment...

@Octachron I suggest that we merge after you fix the conflicts.

Thanks for the rebase. CI report: ``` File "/home/runner/work/ocaml/ocaml/typing/rawprinttyp.ml", line 140, characters 23-27: 140 | match e with None -> fprintf ppf " RFnone" ^^^^ Error: This pattern should not...

The submodule discussion is very fun but I think there are other things to discuss as well, among which: - If a module has several distinct let-operator structures of interest¹,...

> I've definitely been playing a bit fast and loose with the subtle difference between these two approaches -- refering to let* as monadic and let+ as applicative -- but...

Hi @aantron, I hear you, but I think that everyone is wary of rolling back on the sort of consensus on the binding operators that we have managed to gather....

@yallop: fair points, but I would make a distinction between technical design discussions, such as the ones you are reporting in your post, and some syntax choices that are much...

I propose documentation for `caml_result` in the FFI chapter of the manual in #13216.

Note to self: the Coq implementation uses `_exn` functions in its fork of the bytecode interpreter: ``` # /usr/bin/ld: kernel/byterun/libcoqrun_stubs.a(coq_interp.o): in function `coq_interprete': # /home/gasche/Prog/ocaml/github-trunk/_opam/.opam-switch/build/coq-core.8.19.2/_build/default/kernel/byterun/coq_interp.c:582: undefined reference to `caml_process_pending_actions_exn' ```...