Optimize the ABI boundary of wasm-compiled proc macros #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a culmination of the following set of ideas:
I figured these are all large enough changes that this'll want to eventually be bumped to 0.2, so I've started pruning APIs exposed by
watt
in this PR as well. This updates the README with general high-level docs of how to usewatt
as well.This should inch us closer to a "level playing field" between natively compiled procedural macros and wasm-compiled procedural macros when using a JIT!