summaryrefslogtreecommitdiffstats
path: root/tests/coverage/no_spans.coverage
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-19 09:26:03 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-06-19 09:26:03 +0000
commit9918693037dce8aa4bb6f08741b6812923486c18 (patch)
tree21d2b40bec7e6a7ea664acee056eb3d08e15a1cf /tests/coverage/no_spans.coverage
parentReleasing progress-linux version 1.75.0+dfsg1-5~progress7.99u1. (diff)
downloadrustc-9918693037dce8aa4bb6f08741b6812923486c18.tar.xz
rustc-9918693037dce8aa4bb6f08741b6812923486c18.zip
Merging upstream version 1.76.0+dfsg1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'tests/coverage/no_spans.coverage')
-rw-r--r--tests/coverage/no_spans.coverage30
1 files changed, 30 insertions, 0 deletions
diff --git a/tests/coverage/no_spans.coverage b/tests/coverage/no_spans.coverage
new file mode 100644
index 000000000..e55177698
--- /dev/null
+++ b/tests/coverage/no_spans.coverage
@@ -0,0 +1,30 @@
+ LL| |#![feature(coverage_attribute)]
+ LL| |// edition: 2021
+ LL| |
+ LL| |// If the span extractor can't find any relevant spans for a function, the
+ LL| |// refinement loop will terminate with nothing in its `prev` slot. If the
+ LL| |// subsequent code tries to unwrap `prev`, it will panic.
+ LL| |//
+ LL| |// This scenario became more likely after #118525 started discarding spans that
+ LL| |// can't be un-expanded back to within the function body.
+ LL| |//
+ LL| |// Regression test for "invalid attempt to unwrap a None some_prev", as seen
+ LL| |// in issues such as #118643 and #118662.
+ LL| |
+ LL| |#[coverage(off)]
+ LL| |fn main() {
+ LL| | affected_function()();
+ LL| |}
+ LL| |
+ LL| |macro_rules! macro_that_defines_a_function {
+ LL| | (fn $name:ident () $body:tt) => {
+ LL| | fn $name () -> impl Fn() $body
+ LL| | }
+ LL| |}
+ LL| |
+ LL| |macro_that_defines_a_function! {
+ LL| | fn affected_function() {
+ LL| 1| || ()
+ LL| | }
+ LL| |}
+