abrown opened PR #5087 from optional-wiggle-tracing
to main
:
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 onwiggle
,wiggle-macro
, andwiggle-generate
.<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
abrown updated PR #5087 from optional-wiggle-tracing
to main
.
abrown has marked PR #5087 as ready for review.
abrown requested alexcrichton for a review on PR #5087.
alexcrichton closed without merge PR #5087.
alexcrichton reopened PR #5087 from optional-wiggle-tracing
to main
.
abrown updated PR #5087 from optional-wiggle-tracing
to main
.
abrown closed without merge PR #5087.
Last updated: Dec 23 2024 at 12:05 UTC