Ben L. Titzer

@rossberg I think the main argument here is that a builtin comes with its own specification via a standard lowering (i.e. the fallback) which is guaranteed to be semantically equivalent...

I generally agree that such a JIT mechanism will need a way to specify new functions that have access to a module's internals. We definitely don't want to break the...

I don't see a JIT capability necessarily being dependent on function references. One could as well have an API where the result of JITing is inserted into a table at...

@fgmccabe Yes, they can be recursive, but continuation types are defined by referring to a previous heap type index that is required to be a signature. Continutation types can only...

@fgmccabe I think we should avoid anything that necessitates a triple for the value representation. Fat pointers to implement the counter approach is probably my limit; otherwise it would probably...

@rossberg Wizard implements all host -> Wasm calls as a stack switch now. I'm more optimistic that stack switching cost will be cheap enough that this is viable, especially considering...

Ok, I can see how explicit field offsets are effectively part of an ABI, and thus part of a lowering of abstract Wit records. What would be the right way...

FWIW, Virgil has an embedded DSL for specifying memory layouts: https://github.com/titzer/virgil/blob/master/doc/tutorial/Layouts.md

Ok, thanks for taking a look. If it's nontrivial work, don't waste too much time on it. > Won't these clients have to be adapted anyway? Otherwise they won't be...

1. All things related to floating point environment, `fegetenv` should be stubbed to nops on Wasm.