3 The tracking issue for this feature is: [#84605]
5 [#84605]: https://github.com/rust-lang/rust/issues/84605
9 The `no_coverage` attribute can be used to selectively disable coverage
10 instrumentation in an annotated function. This might be useful to:
12 - Avoid instrumentation overhead in a performance critical function
13 - Avoid generating coverage for a function that is not meant to be executed,
14 but still target 100% coverage for the rest of the program.
19 #![feature(no_coverage)]
21 // `foo()` will get coverage instrumentation (by default)