File: opaque-upvar.rs

package info (click to toggle)
rustc 1.88.0%2Bdfsg1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 934,128 kB
  • sloc: xml: 158,127; python: 36,062; javascript: 19,855; sh: 19,700; cpp: 18,947; ansic: 12,993; asm: 4,792; makefile: 690; lisp: 29; perl: 29; ruby: 19; sql: 11
file content (19 lines) | stat: -rw-r--r-- 800 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
//@ check-pass
//@ revisions: current next
//@ ignore-compare-mode-next-solver (explicit revisions)
//@[next] compile-flags: -Znext-solver

// Regression test for <https://github.com/rust-lang/trait-system-refactor-initiative/issues/197>.
// This is only an issue in the new solver, but I'm testing it in both solvers for now.
// This has to do with the fact that the recursive `walk_dir` is a revealing use, which has not
// yet been constrained from the defining use by the time that closure signature inference is
// performed. We don't really care, though, since anywhere we structurally match on a type in
// upvar analysis, we already call `structurally_resolve_type` right before `.kind()`.

fn walk_dir(cb: &()) -> impl Sized {
    || {
        let fut = walk_dir(cb);
    };
}

fn main() {}