Files

Pat Hickey 2702619427 wiggle: allow disable tracing in Wiggle-generated code (#5146 )

Wiggle generates code that instruments APIs with tracing code. This is
handy for diagnosing issues at runtime, but when inspecting the output
of Wiggle, it can make the generated code difficult for a human to
decipher. This change makes tracing a default but optional feature,
allowing users to avoid tracing code with commands like `cargo expand
--no-default-features`. This should be no change for current crates
depending on `wiggle`, `wiggle-macro`, and `wiggle-generate`.

review: add 'tracing' feature to wasi-common

review: switch to using macro configuration parsing

Co-authored-by: Andrew Brown <andrew.brown@intel.com>

2022-10-27 11:26:54 -07:00

src

wiggle: allow disable tracing in Wiggle-generated code (#5146 )

2022-10-27 11:26:54 -07:00

Cargo.toml

Leverage Cargo's workspace inheritance feature (#4905 )

2022-09-26 11:30:01 -05:00

LICENSE

Shuffle around the wiggle crates (#1414 )

2020-03-26 18:34:50 -05:00

README.md

Shuffle around the wiggle crates (#1414 )

2020-03-26 18:34:50 -05:00

README.md

wiggle-generate

This is a library crate that implements all of the component parts of the wiggle proc-macro crate.

Code lives in a separate non-proc-macro crate so that it can be reused in other settings, e.g. the lucet-wiggle crate.

Code generated by this crate should not have any references to a particular WebAssembly runtime or engine. It should instead expose traits that may be implemented by an engine. Today, it is consumed by both Lucet and Wasmtime.