cd9021e8cb
When we try to extract coverage-relevant spans from MIR, sometimes we see MIR statements/terminators whose spans cover the entire function body. Those spans tend to be unhelpful for coverage purposes, because they often represent compiler-inserted code, e.g. the implicit return value of `()`.
35 lines
1.2 KiB
Plaintext
35 lines
1.2 KiB
Plaintext
Function name: coverage_attr_closure::GLOBAL_CLOSURE_ON::{closure#0}
|
|
Raw bytes (9): 0x[01, 01, 00, 01, 01, 06, 0f, 02, 02]
|
|
Number of files: 1
|
|
- file 0 => global file 1
|
|
Number of expressions: 0
|
|
Number of file 0 mappings: 1
|
|
- Code(Counter(0)) at (prev + 6, 15) to (start + 2, 2)
|
|
|
|
Function name: coverage_attr_closure::contains_closures_off::{closure#0} (unused)
|
|
Raw bytes (9): 0x[01, 01, 00, 01, 00, 1d, 13, 02, 06]
|
|
Number of files: 1
|
|
- file 0 => global file 1
|
|
Number of expressions: 0
|
|
Number of file 0 mappings: 1
|
|
- Code(Zero) at (prev + 29, 19) to (start + 2, 6)
|
|
|
|
Function name: coverage_attr_closure::contains_closures_on
|
|
Raw bytes (19): 0x[01, 01, 00, 03, 01, 0f, 01, 01, 1a, 01, 05, 09, 00, 1b, 01, 04, 01, 00, 02]
|
|
Number of files: 1
|
|
- file 0 => global file 1
|
|
Number of expressions: 0
|
|
Number of file 0 mappings: 3
|
|
- Code(Counter(0)) at (prev + 15, 1) to (start + 1, 26)
|
|
- Code(Counter(0)) at (prev + 5, 9) to (start + 0, 27)
|
|
- Code(Counter(0)) at (prev + 4, 1) to (start + 0, 2)
|
|
|
|
Function name: coverage_attr_closure::contains_closures_on::{closure#0} (unused)
|
|
Raw bytes (9): 0x[01, 01, 00, 01, 00, 11, 13, 02, 06]
|
|
Number of files: 1
|
|
- file 0 => global file 1
|
|
Number of expressions: 0
|
|
Number of file 0 mappings: 1
|
|
- Code(Zero) at (prev + 17, 19) to (start + 2, 6)
|
|
|