rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
647f1536d2f50b203ca9a67396225c4f7771e1c8
rust/tests/coverage/macro_in_closure.cov-map

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
913 B
Plaintext
Raw Normal View History

coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Function name: macro_in_closure::NO_BLOCK::{closure#0}
coverage: Build an "expansion tree" and use it to unexpand raw spans
2025-08-16 17:46:05 +10:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 07, 1c, 00, 24, 01, 00, 25, 00, 2c]
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Number of files: 1
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 17:36:50 +10:00
- file 0 => $DIR/macro_in_closure.rs
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Number of expressions: 0
coverage: Build an "expansion tree" and use it to unexpand raw spans
2025-08-16 17:46:05 +10:00
Number of file 0 mappings: 2
- Code(Counter(0)) at (prev + 7, 28) to (start + 0, 36)
- Code(Counter(0)) at (prev + 0, 37) to (start + 0, 44)
coverage: Include the highest counter ID seen in `.cov-map` dumps 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.)
2024-10-08 13:13:05 +11:00
Highest counter ID seen: c0
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Function name: macro_in_closure::WITH_BLOCK::{closure#0}
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 17:52:55 +10:00
Raw bytes (24): 0x[01, 01, 00, 04, 01, 09, 1e, 00, 1f, 01, 01, 05, 00, 0d, 01, 00, 0e, 00, 15, 01, 01, 01, 00, 02]
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Number of files: 1
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 17:36:50 +10:00
- file 0 => $DIR/macro_in_closure.rs
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Number of expressions: 0
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 17:52:55 +10:00
Number of file 0 mappings: 4
- Code(Counter(0)) at (prev + 9, 30) to (start + 0, 31)
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 13)
- Code(Counter(0)) at (prev + 0, 14) to (start + 0, 21)
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 2)
coverage: Include the highest counter ID seen in `.cov-map` dumps 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.)
2024-10-08 13:13:05 +11:00
Highest counter ID seen: c0
coverage: Test for closure body that is a single bang-macro
2024-01-22 13:56:37 +11:00
Reference in New Issue Copy Permalink