File: no_spans_if_not.coverage

package info (click to toggle)
rustc 1.85.0%2Bdfsg3-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental, sid, trixie
  • size: 893,396 kB
  • sloc: xml: 158,127; python: 35,830; javascript: 19,497; cpp: 19,002; sh: 17,245; ansic: 13,127; asm: 4,376; makefile: 1,051; perl: 29; lisp: 29; ruby: 19; sql: 11
file content (30 lines) | stat: -rw-r--r-- 1,146 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   LL|       |//@ edition: 2021
   LL|       |
   LL|       |// If the span extractor can't find any relevant spans for a function,
   LL|       |// but the function contains coverage span-marker statements (e.g. inserted
   LL|       |// for `if !`), coverage codegen may think that it is instrumented and
   LL|       |// consequently complain that it has no spans.
   LL|       |//
   LL|       |// Regression test for <https://github.com/rust-lang/rust/issues/118850>,
   LL|       |// "A used function should have had coverage mapping data but did not".
   LL|       |
   LL|      1|fn main() {
   LL|      1|    affected_function();
   LL|      1|}
   LL|       |
   LL|       |macro_rules! macro_that_defines_a_function {
   LL|       |    (fn $name:ident () $body:tt) => {
   LL|       |        fn $name () $body
   LL|       |    }
   LL|       |}
   LL|       |
   LL|       |macro_that_defines_a_function! {
   LL|      1|    fn affected_function() {
   LL|      1|        if !false {
   LL|      1|            ()
   LL|       |        } else {
   LL|      0|            ()
   LL|       |        }
   LL|       |    }
   LL|       |}