Dan Gohman
Dan Gohman
As [commented](https://github.com/WebAssembly/design/issues/1520#issuecomment-2231445691), the CG decided to raise the Web implementation limits on the number of imports and exports to one million. https://github.com/WebAssembly/spec/pull/1766 is tracking updating the spec. See also https://github.com/WebAssembly/design/issues/1225...
I approve this license change.
I've now added a patch which fixes https://github.com/llvm/llvm-project/issues/63755.
> Can you split this patch into a separate PR? Sure, I've now created https://github.com/llvm/llvm-project/pull/112617 with just the that patch.
An example of pulling a function out of `rustix::runtime` is https://github.com/bytecodealliance/rustix/pull/1133. In making the function public, we're renaming it from the Linux-specific `exit_group` to the more descriptive `immediately_exit`, implementing it...
I should also say, PRs are welcome but not necessary here. Just posting a comment here would be helpful!
I had pictured it as a canonical built-in, something like this: ```wat (component (core memory $memory (canon memory.define 1 1)) (core module $M (import "memory-instance" "memory" (memory 1 1)) )...
I don't know how it could be possible to expose a lower-level API while still having any of the benefits of type, memory, or I/O safety. To provide a safe...
That's a good point. And I guess it's ok even if Linux adds arbitrary new types in the future, because users still need an `unsafe` block to convert from bytes...