@mcc @whitequark wait are you talking about stuff that might be crossing over into wasm components here?
@mcc @whitequark wait are you talking about stuff that might be crossing over into wasm components here?
@mcc @whitequark (also not sure if you’re aware of wizer and weval)
@zkat @whitequark I have not heard of either of these things.
@mcc @whitequark one is a partial evaluator, the other executes the init function for a wasm module and snapshots the result, so when you run the snapshot it starts after all the setup has been done
@zkat @whitequark I don't know. I don't know how to use wasm components.
@mcc @whitequark they expose and consume genetic interfaces defined in a language called WIT, which you can have bindings for in a language-agnostic manner. They’re designed such that they support a lot of the higher level type stuff Rust does, like sum types aka fancy enums, but you don’t have to worry about shenanigans when consuming/producing this stuff. A component written in one language can connect with one in any other language
@zkat @whitequark If this works, it might obviate what I was wanting to write. I don't know.
@mcc @whitequark I mean if all it does is help show you some prior art I’m happy :)
@mcc @whitequark @TartanLlama wrote an excellent post about it that goes step by step: https://tartanllama.xyz/posts/wasm-plugins/
A space for Bonfire maintainers and contributors to communicate