joeshaw opened PR #5194 from joeshaw/suppress-tracing
to main
:
This replaces the simple
tracing
boolean from thefrom_witx!
macro
with asuppress_tracing
value that can be set on a per-function basis.The format is the same as the
async
value, so functions can either be
listed individually in braces or all tracing can be disabled with*
.
Some identifiers in code were renamed for this reuse:AsyncFunctions
->Functions
andAsyncConfField
->FunctionField
.Examples:
wiggle::from_witx!({ suppress_tracing: *, witx: ["..."], });
wiggle::from_witx!({ suppress_tracing: { module1::func, module2::another_func, }, witx: ["..."], });
Fixes #5193
<!--
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.
-->
pchickey requested pchickey for a review on PR #5194.
joeshaw updated PR #5194 from joeshaw/suppress-tracing
to main
.
joeshaw edited PR #5194 from joeshaw/suppress-tracing
to main
:
This adds to the
tracing
boolean from thefrom_witx!
macro adisabled_for
list of identifiers that allow for suppression of tracing on a per-function basis.Example:
wiggle::from_witx!({ tracing: true disable_for { module1::func, module2::another_func, }, witx: ["..."], });
Fixes #5193
<!--
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.
-->
joeshaw has marked PR #5194 as ready for review.
pchickey submitted PR review.
pchickey merged PR #5194.
Last updated: Nov 22 2024 at 17:03 UTC