Christof Petig
Christof Petig
With respect to wit-vector: `wit-vector` is an owning handle (much like `std::vector`, but compatible with Rust as you can turn it into a malloced pointer and a length and then...
PS: Please keep in mind that I am mostly targeting "code a minimal adapter in C++ and quickly get back to the sunny Rust side" scenarios, so usability on the...
> Would you prefer to land this and iterate in-tree? Or would you prefer to follow-up with anything here before doing so? After working on this for two years out...
Neat idea! I guess this was partially foreshadowed by adding more and more i32 handles representing external data to the canonical ABI over the past year (first resources, then recently...
> I.e.: the component model wants to be able to validate+transcode+copy strings in a single pass. I fear that this would require partial lazy read (and still some sort of...
I was ruminating on a proper (Rust) API for lazy value lowering and realized that what I am really looking for is to remove heap allocations from function calls, so...
This also updates to wasm-tools 0.230.0
@alexcrichton if you look for updating wasm-tools in wac this pull request includes updating to 0.230.0
Closer inspection this evening showed that encoding.rs would need special handling for fixed size lists, so I guess it is incomplete as is, sorry!
But honestly I don't trust my understanding of all the code base involved until the tests in wit-bindgen come out ok, which requires more work on wit-bindgen and wasmtime. As...