wasmtime

You should look at embedding Wasmtime into your C. https://github.com/bytecodealliance/wasmtime/tree/main/examp...

For the audience that would be looking to use the WASM Component Model, and not be an infrastructure implementer of it, whether or not they meet some definition of a method, the component model does define things called resources [1] that have "methods". You'll hold a "handle" to it like you would in your own programming language with the expected drop and/or GC semantics (once implemented [2]) because code is generated to access it like any other FFI like C/C++. With that in mind, the other confusing thing one may come across is composition vs linking within your WASM runtime that supports the Component Model. When you hear "composition" think of compile-time merging of libraries such that the bundle may have less unresolved dependencies of WASM code/implemented component interfaces. Anything unresolved needs to be linked at runtime with

Since you're using Rust, the Cranelift JIT compiler implements something like this[0] to construct an e-graph for its expression rewriting subsystem called ISLE, however if I'm not mistaken it is for disjoint sets (not intervals), and therefore it does not deal with ordering. Maybe you can adapt it for your use case and add those new constraints in? Keep in mind though that this was not written to be in the hot-path itself, you could probably do significantly better by pouring your soul into the SIMD rabbit hole (though SIMD in Rust is usually very annoying to write) Best of luck, hope this helps! [0] https://github.com/bytecodealliance/wasmtime/blob/7dcb9bd6ea...

Just a documentation change, fortunately: https://github.com/bytecodealliance/wasmtime/commits?author=... They've submitted little documentation tweaks to other projects, too; for example: https://learn.microsoft.com/en-us/cpp/overview/whats-new-cpp... I don't know whether this is a formerly-legitimate open source contributor who went rogue, or a deep-cover persona spreading innocuous-looking documentation changes around to other projects as a smokescreen.

As far as I know, you should be able to generate textual CLIF files and feed them to Cranelift: https://github.com/bytecodealliance/wasmtime/blob/main/crane...

As long as this is happening, might as well try some of my favorites: https://github.com/wasm3/wasm3, https://github.com/WebAssembly/wabt, https://github.com/bytecodealliance/wasmtime

When you say wasm container, you mean something like wasmtime that provides a non-browser wasm runtime? https://github.com/bytecodealliance/wasmtime