Hey, I'm trying to use wit-bindgen to create a module that will be used in both node and python, but currently I an error thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', crates/c-api/src/linker.rs:105:80
when I try to call any function in the generated bindings. I hope we can use this as a tool until wasm-bindgen gets back into wasmtime-py
@bjorn3 answered the underlying issue here, was context needs to be set.
Jens Gåsemyr Magnus has marked this topic as resolved.
I was looking at the wit-parser
crate and noticed the Interface
Token/AST. Is this still a thing or a future thing?
At the moment, they're a potential future thing.
Hey everyone, love the project! I am looking to implement rust plugins where the guests and host would be written in rust. The idea is to have an indexer (server listening to blockhain events) that can use plugins that handle writing to different data stores. This would be an open source project for anyone to run their own indexers, so I want to confirm the rust APIs are stable enough to use for this purpose. For a little more information on the application, I essentially just need a single function for interfacing but it would need to transfer a large nested complex type consisting of Options, Vectors, Strings, [u8]'s, Enums, and a bunch of primitives. Thanks
Options, Strings, [u8]s, Enums, and primitive values are all usable at this point. Whether the APIs are stable enough probably depends on your specific needs.
Last updated: Dec 23 2024 at 13:07 UTC