| Age | Commit message (Collapse) | Author | Lines |
|---|
|
When making changes that have a large impact on coverage counter creation, this
makes it easier to see whether the number of physical counters has changed.
(The highest counter ID seen in coverage maps is not necessarily the same as
the number of physical counters actually used by the instrumented code, but
it's the best approximation we can get from looking only at the coverage maps,
and it should be reasonably accurate in most cases.)
|
|
|
|
By moving `block_on` to an auxiliary crate, we avoid having to keep a separate
copy of it in every async test.
(This also incorporates some small tweaks to the headers in `await_ready.rs`.)
|
|
This makes it possible to treat more kinds of nested item/code as holes,
instead of being restricted to closures.
|
|
|
|
|
|
This performs the same task as the hole-carving code in the main span refiner,
but in a separate earlier pass.
|
|
Some of these cases currently don't occur in practice, but are included for
completeness, and to avoid having to add them later as branch coverage and
MC/DC coverage start building more complex expressions.
|
|
|
|
This improves the coverage instrumentation of closures declared in macros, as
seen in `closure_macro.rs` and `closure_macro_async.rs`.
|
|
These tests can simply be reformatted as normal, because the resulting changes
are unimportant.
|
|
|
|
|
