rust/tests/coverage/no_spans.cov-map

Function name: no_spans::affected_function
Raw bytes (9): 0x[01, 01, 00, 01, 01, 15, 1c, 00, 1d]
Number of files: 1
- file 0 => $DIR/no_spans.rs
Number of expressions: 0
Number of file 0 mappings: 1
- Code(Counter(0)) at (prev + 21, 28) to (start + 0, 29)
Highest counter ID seen: c0

Function name: no_spans::main
Raw bytes (19): 0x[01, 01, 00, 03, 01, 0a, 01, 00, 0a, 01, 01, 05, 00, 1a, 01, 01, 01, 00, 02]
Number of files: 1
- file 0 => $DIR/no_spans.rs
Number of expressions: 0
Number of file 0 mappings: 3
- Code(Counter(0)) at (prev + 10, 1) to (start + 0, 10)
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 26)
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 2)
Highest counter ID seen: c0
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 13:30:31 +00:00			`Function name: no_spans::affected_function`
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 07:52:55 +00:00			`Raw bytes (9): 0x[01, 01, 00, 01, 01, 15, 1c, 00, 1d]`
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 13:30:31 +00:00			`Number of files: 1`
coverage-dump: Dump filenames instead of global file IDs (and bless) 2025-04-24 07:36:50 +00:00			`- file 0 => $DIR/no_spans.rs`
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 13:30:31 +00:00			`Number of expressions: 0`
			`Number of file 0 mappings: 1`
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 07:52:55 +00:00			`- Code(Counter(0)) at (prev + 21, 28) to (start + 0, 29)`
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 02:13:05 +00:00			`Highest counter ID seen: c0`
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 13:30:31 +00:00
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 07:52:55 +00:00			`Function name: no_spans::main`
			`Raw bytes (19): 0x[01, 01, 00, 03, 01, 0a, 01, 00, 0a, 01, 01, 05, 00, 1a, 01, 01, 01, 00, 02]`
coverage: Regression test for unwrapping `prev` when there are no spans 2023-12-08 04:51:06 +00:00			`Number of files: 1`
coverage-dump: Dump filenames instead of global file IDs (and bless) 2025-04-24 07:36:50 +00:00			`- file 0 => $DIR/no_spans.rs`
coverage: Regression test for unwrapping `prev` when there are no spans 2023-12-08 04:51:06 +00: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 07:52:55 +00:00			`Number of file 0 mappings: 3`
			`- Code(Counter(0)) at (prev + 10, 1) to (start + 0, 10)`
			`- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 26)`
			`- 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 02:13:05 +00:00			`Highest counter ID seen: c0`
coverage: Regression test for unwrapping `prev` when there are no spans 2023-12-08 04:51:06 +00:00