watt
watt copied to clipboard
dtolnay
Runtime for executing procedural macros as WebAssembly
Hello, Following discussions on IRC, I've been pointed to this crate. It looks great! That said, there is a thing that is listed in the readme, and, I think, has...
I have a macro I want to run through watt (in fact, I need to in order to break a self-dependency bootstrap cycle). However, I additionally want to have the...
Panics seem to get printed decently by the interpreted runtime, but not the JIT runtime. To reproduce, cherry-pick 149ca1a421e461ecb1f88cb1b37fcceb9dd6b653 and then: ```console $ cargo build --release --target wasm32-unknown-unknown --manifest-path demo/impl/Cargo.toml...
Right now there's rudimentary support for executing code in a JIT loaded through a dynamic library which exposes a wasm C API. Unfortunately though there's not really a great way...
In the non-JIT runtime let's time how long each macro call takes and print a message if any one takes too long, pointing to the JIT installation instructions and explaining...
From some rough tests, Watt macro expansion when compiling the runtime in release mode is about 15x faster than when the runtime is compiled in debug mode. Maybe we can...
More than half of the (uncompressed) .wasm file of `wa-serde-derive` is made up of the debug info section.
It seems that panic information is still compiled into the wasm file. The crate file can be downloaded from this [link](https://d19xqa3lc3clo8.cloudfront.net/crates/wa-serde-derive/wa-serde-derive-0.1.101.crate). It contains the wasm file (2.7 MB uncompressed). If...
We'll want to take some representative proc macro(s) to compile to wasm, and set up a benchmark that times how long it takes to expand some representative inputs. This would...
Hello, I hope you having a wonderful day, First off let me thank you for your awesome projects; I'm a fan of your work. I was wondering have you ever...
