Ben L. Titzer
Ben L. Titzer
This is already updated in sexpr-wasm-prototype, so maybe just wasm-e2e needs to be updated.
Just as a datapoint, the threads proposal includes ~70 instructions, including read-modify-write variants of memory accesses, as well as futex operations. For engines and platforms that can't or won't offer...
I agree that getting "the one instruction" inlined into the final machine code is necessary to get the performance benefits. It's likely the cost of a function call would erase...
> I agree it moves non-determinism around, but allows the module consumer (which is recursive down to the end user) to pick the tradeoff that actually has knowledge of the...
> It worth to add, before anyone will mention partial function recompilation or code patching, that current implementation works closely with compiler's register allocator: to fit registers into instruction limitations...
@rossberg Curious if you have thoughts here.
> Overload resolution in languages like Java is done at compile time. Common practice is to import overloads with different mangled names. It can only be done at compile time...
> I would argue that mangled names are used exactly to avoid that. Compilers resolve overloads during separate compilation and use mangled names to express this resolution result. Sure, but...
Importing non-reference types is something we need to support in the long term. I think it's OK to have a restriction for now, but type imports are a form of...