Skip to content

Commit 6264030

Browse files
committed
Rename test to unresolvable-upvar-issue-87987.rs and add some notes
1 parent 67ff215 commit 6264030

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

src/tools/tidy/src/issues.txt

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -409,7 +409,6 @@ ui/closure_context/issue-26046-fn-once.rs
409409
ui/closure_context/issue-42065.rs
410410
ui/closures/2229_closure_analysis/issue-118144.rs
411411
ui/closures/2229_closure_analysis/issue-87378.rs
412-
ui/closures/2229_closure_analysis/issue-87987.rs
413412
ui/closures/2229_closure_analysis/issue-88118-2.rs
414413
ui/closures/2229_closure_analysis/issue-88476.rs
415414
ui/closures/2229_closure_analysis/issue-89606.rs

tests/ui/closures/2229_closure_analysis/issue-87987.rs renamed to tests/ui/closures/2229_closure_analysis/unresolvable-upvar-issue-87987.rs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
//! When a closure syntactically captures a place, but doesn't actually capture
2+
//! it, make sure MIR building doesn't ICE when handling that place.
3+
//!
4+
//! Under the Rust 2021 disjoint capture rules, this sort of non-capture can
5+
//! occur when a place is only inspected by infallible non-binding patterns.
6+
17
//@ run-pass
28
//@ edition:2021
39

0 commit comments

Comments
 (0)