summaryrefslogtreecommitdiffstats
path: root/tests/coverage/no_spans_if_not.coverage
diff options
context:
space:
mode:
Diffstat (limited to 'tests/coverage/no_spans_if_not.coverage')
-rw-r--r--tests/coverage/no_spans_if_not.coverage30
1 files changed, 30 insertions, 0 deletions
diff --git a/tests/coverage/no_spans_if_not.coverage b/tests/coverage/no_spans_if_not.coverage
new file mode 100644
index 000000000..1b6bbc75a
--- /dev/null
+++ b/tests/coverage/no_spans_if_not.coverage
@@ -0,0 +1,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| | fn affected_function() {
+ LL| | if !false {
+ LL| | ()
+ LL| | } else {
+ LL| | ()
+ LL| | }
+ LL| | }
+ LL| |}
+