Gabriel Scherer

Re. layout computation and invalid recursive references: we have the same issue in our computation of "head shapes" for unboxed type constructors. There are "malign" cycles that clearly must be...

This being said, the comparison may not go all the way, because if we look at the case of "potentially-malign cycle hidden under an abstraction", ```ocaml type t = Foo...

(The issue where we discussed this, in particular Stephen's excellent observation, is https://github.com/ocaml/ocaml/issues/10485 .)

My impression from the dev-meeting discussion we had was that there was a sort of consensus on leaving the backend out for a first iteration, and concentrating on a symbol...

Thanks for the pointer. From looking at it briefly, I cannot tell whether I would recommend trying to use explicit uniform arrays for this purpose. The "methods" array seems to...

> I believe that you can get a correct implementation by using Obj.new_block for Uniform_array.make, and regular array functions for all the rest. If you want an extra bit of...

Coq/Rocq also includes a small module of uniform arrays in its codebase, as part of the definition of its "persistent arrays": https://github.com/coq/coq/blob/d7d392191a367839b0f5a7772e48b8f24e9f1b3e/kernel/parray.ml . My understanding is that the need for...

To summarize, your proposal is as follows: 1. Integrate Lexifi's work on direct binary generation in the compiler upstream. 2. Add the necessary linker logic to use it from ocamlnat....

Thanks for the change! I still think this is a very nice project and I'm glad to get the update. In the interest of starting the bikeshedding early: I'm not...

@NathanReb would you by chance have some information on the current status of the native-toplevel revival? The "unify the toploop implementations" part was done (in large part) in #10124. Were...