Gabriel Scherer

I hope we can find the manpower to complement @whitequark here, but I haven't been able to help much myself with the compiler distribution release work. (cc @let-def)

To complement @whitequark answer: ideally we would indeed have support for some forms of GADTs (some subsets may be easier to handle than others, and some plugins may make this...

The requirement/need/wish seems very sensible to me. Two remarks: - The error-reporting scheme should not hurt performance too much. I am highly confident that it's possible to have both at...

I believe that this PR would need the following to make progress: - The original author, @gleroi, should say whether they would be available to work again on their PR...

Two more people have asked about this feature on the #ocaml IRC channel yesterday, Algebr and @AltGr .

There has been a good amount of research work on type-directed or shape-directed unboxing, supported by code specialization. For a recent example, see the work on call-graph-based specialization of (boxed)...

> First, until we invent JIT and other features, the current Wasm, even when including the current GC proposal, is an entirely static, dare I say "closed world" system, with...

@aardappel > Yes, but the types at the edges are currently very basic types that may well not make it possible to express the full set of type feature of...

@RossTate here is another argument that you may find interesting, in terms of finding a "principled" argument for choosing one size or the other. We are talking about splits in...

Here would be an artificial example: ```ocaml (* a fairly inefficient way to compute 2^n, by creating a full tree of depth n and counting its leaves *) let pow2...