Guy Bedford
Guy Bedford
Since the Wasm CSP proposal is Phase 3, it seems prudent to make a note now as to how the ESM Integration interacts with the CSP proposal. Depending on which...
In https://github.com/bytecodealliance/jco/pull/262, we now validate all borrows properly. The need to call `resource[Symbol.dispose]()` explicitly for all functions that take resources seems unnecessary though. Rather, the implementation should always auto-drop borrows...
Brought up at CTW - Spidermonkey has a debugger API that we should figure out the right integration for. Unfortunately it does not include a debugging protocol itself, so one...
One of the trickiest parts of a ComponentizeJS workflow is figuring out the write structure to author the code to. We should generate the boilerplate outline for the world being...
When using say a restricted error variant, throwing an unsupported error will be masked by the "invalid variant" error in the bindings. In componentize bindings, we should specially handle invalid...
We should automatically support a TypeScript input and also having dependencies being bundled in as well, down to imports not colliding with the world imports.
`console` logging should be going through wasi-logging, either by default or as an option.
The current GC strategy is to just clear all allocations at the end of each call, but we need to allow the JS ArrayBuffers to hold on to the memory...
Implementing a clock subscribe function that can be polled to be accurate to more than 2ms isn't necessarily straightforward. It might be worth adding a note, that this is not...
It could be worth further clarifying the drop & abort behaviours at various stages of the lifecycle of a request and response concretely, since these are observable implementation details in...