rust/tests/coverage/attr/off-on-sandwich.cov-map, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-05-06T10:42:25+00:00coverage: Only merge adjacent coverage spans2025-05-06T10:42:25+00:00ZalatharZalathar@users.noreply.github.com2025-04-12T07:52:55+00:00urn:sha1:4d5a1acebfe031ca2af75786295a2cd2a0633943
This also removes some manipulation of the function signature span that only
made sense in the context of merging non-adjacent spans.
coverage-dump: Dump filenames instead of global file IDs (and bless)2025-05-06T01:58:58+00:00ZalatharZalathar@users.noreply.github.com2025-04-24T07:36:50+00:00urn:sha1:c53a76743c01afa356ae5301bc1b35044354da7acoverage: Shrink call spans to just the function name2025-04-01T02:07:33+00:00ZalatharZalathar@users.noreply.github.com2025-03-29T10:33:01+00:00urn:sha1:577272eedeaace00aa695135b3b8fee3768536a5
This is a way to shrink call spans that doesn't involve mixing different spans,
and avoids overlap with argument spans.
This patch also removes some low-value comments that were causing rustfmt to
ignore the match arms.
Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, r=wesleywiser"2024-12-23T01:30:37+00:00ZalatharZalathar@users.noreply.github.com2024-12-22T03:26:54+00:00urn:sha1:87c2f9a5be900e835f3c41cec2886d54ec0ca012
This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing
changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
Add reference annotations for the `coverage` attribute2024-12-18T23:03:44+00:00Eric Husseric@huss.org2024-12-18T23:03:44+00:00urn:sha1:dbf5ae3a864f555cfe6770896a23f7dea77fb6fbStabilize #[coverage] attribute2024-12-17T02:07:06+00:00ltdkusr@ltdk.xyz2024-09-23T23:40:22+00:00urn:sha1:cb487cc2fa3c5ebfddd22d6721cf1669943c1774coverage: 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.