rust/tests/coverage/no_spans.cov-map

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

Function name: no_spans::affected_function::{closure#0}
Raw bytes (9): 0x[01, 01, 00, 01, 01, 1b, 0c, 00, 0e]
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
- Code(Counter(0)) at (prev + 27, 12) to (start + 0, 14)
Highest counter ID seen: c0
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 07:30:31 -06:00			`Function name: no_spans::affected_function`
			`Raw bytes (9): 0x[01, 01, 00, 01, 01, 1a, 1c, 00, 1d]`
			`Number of files: 1`
			`- file 0 => global file 1`
			`Number of expressions: 0`
			`Number of file 0 mappings: 1`
			`- Code(Counter(0)) at (prev + 26, 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-07 21:13:05 -05:00			`Highest counter ID seen: c0`
macro_rules: Preserve all metavariable spans in a global side table 2023-12-26 07:30:31 -06:00
coverage: Regression test for unwrapping `prev` when there are no spans 2023-12-07 22:51:06 -06:00			`Function name: no_spans::affected_function::{closure#0}`
			`Raw bytes (9): 0x[01, 01, 00, 01, 01, 1b, 0c, 00, 0e]`
			`Number of files: 1`
			`- file 0 => global file 1`
			`Number of expressions: 0`
			`Number of file 0 mappings: 1`
			`- Code(Counter(0)) at (prev + 27, 12) to (start + 0, 14)`
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-07 21:13:05 -05:00			`Highest counter ID seen: c0`
coverage: Regression test for unwrapping `prev` when there are no spans 2023-12-07 22:51:06 -06:00