rust/tests/coverage/attr/nested.cov-map, branch 1.85.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.85.02024-12-18T23:03:44+00:00Add reference annotations for the `coverage` attribute2024-12-18T23:03:44+00:00Eric Husseric@huss.org2024-12-18T23:03:44+00:00urn:sha1:dbf5ae3a864f555cfe6770896a23f7dea77fb6fbcoverage: Include the highest counter ID seen in `.cov-map` dumps2024-10-11T10:04:37+00:00ZalatharZalathar@users.noreply.github.com2024-10-08T02:13:05+00:00urn:sha1:599f95ecc26fb68cccbf79780dd1825a4cf73eb0
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.)
coverage: Extract hole spans from HIR instead of MIR2024-07-08T11:22:56+00:00ZalatharZalathar@users.noreply.github.com2024-07-01T03:29:54+00:00urn:sha1:63c04f05e60ce27311fc1b874907188616beb558
This makes it possible to treat more kinds of nested item/code as holes,
instead of being restricted to closures.
coverage: Apply `#[coverage(..)]` recursively to nested functions2024-06-26T00:08:05+00:00ZalatharZalathar@users.noreply.github.com2024-06-22T06:34:24+00:00urn:sha1:3262611cc5db7ce83dee4268fb1901311b24e5fcAdd more thorough coverage tests for `#[coverage(..)]` in nested functions2024-06-18T11:27:34+00:00ZalatharZalathar@users.noreply.github.com2024-06-18T10:02:21+00:00urn:sha1:50936586323eefb6504945f444fe9e4928f2bb86
These tests reflect the current implementation behaviour, which is not
necessarily the desired behaviour.