File: dont-ice-when-body-tainted-by-errors.rs

package info (click to toggle)
rustc 1.85.0%2Bdfsg3-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental, forky, 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 (21 lines) | stat: -rw-r--r-- 792 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
//@ edition: 2021

struct DropMe;

trait Impossible {}
fn trait_error<T: Impossible>() {}

pub fn main() {
    let b = DropMe;
    let async_closure = async move || {
        // Type error here taints the environment. This causes us to fallback all
        // variables to `Error`. This means that when we compute the upvars for the
        // *outer* coroutine-closure, we don't actually see any upvars since `MemCategorization`
        // and `ExprUseVisitor`` will bail early when it sees error. This means
        // that our underlying assumption that the parent and child captures are
        // compatible ends up being broken, previously leading to an ICE.
        trait_error::<()>();
        //~^ ERROR the trait bound `(): Impossible` is not satisfied
        let _b = b;
    };
}