Guy Bedford
Guy Bedford
Jco has prioritised correctness over performance. As adoption grows, we will need to investigate performance more carefully, both for code generation and for host call overhead. The first step here...
Now that source phase imports are at phase 3 we can consider what it would look like to output for this target. In addition this would also unlock cloudflare worker...
We should be stricter about traps in jco. When a component traps it moves into a trapped state and is no longer callable, so this should be a flagged state...
This one comes out of discussion with @dbaeumer on the base-level type implementations. Currently we implement flags as an object of bools, the suggestion would be switch to implementing all...
After discussing this one with @dbaeumer, I think there might be merit in having some kind of first-class runtime primitives for enums and variants. So instead of passing a string...
As also discussed at CTW, The ComponentizeJS has a need for code scaffolding of the JavaScript / TypeScript code for a given interface. @eduardomourar suggested that if we had such...
When generating many functions with similar bindgen, there tends to be a lot of repeated code. This is by design of the bindgen process, and output size is not currently...
This one caught me off-guard and seems like an easy footgun. Passing `[1,2,3]` into a `Vec` by mistake should give a clear error (or coercion?).
In https://github.com/bytecodealliance/wit-bindgen/pull/406, having imports treated as ES module imports, results in their types no longer being asserted. The problem is how to assert the imported types, as opposed to the...
Currently documentation for the project is very minimal. This includes both for using jco and contributing to jco (tracked in https://github.com/bytecodealliance/jco/issues/62). Thanks to @divya-mohan0209 for raising this topic more broadly,...