about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/alloc_example.rs
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2021-09-30 23:41:08 -0700
committerGitHub <noreply@github.com>2021-09-30 23:41:08 -0700
commit8c5114b4e84a5a707c071982e3357fcbb3fb0a75 (patch)
tree421b457d0454d60efb399ea5df29b6676a692bd4 /compiler/rustc_codegen_gcc/example/alloc_example.rs
parent27269554b85d9202f5cdbfa09c6350498adf9d31 (diff)
parent87a4a79554b03e2002691b8734d23fb7a556fab1 (diff)
downloadrust-8c5114b4e84a5a707c071982e3357fcbb3fb0a75.tar.gz
rust-8c5114b4e84a5a707c071982e3357fcbb3fb0a75.zip
Rollup merge of #89327 - oli-obk:nll_diag_infer_vars, r=wesleywiser
Pick one possible lifetime in case there are multiple choices

In case a lifetime variable is created, but doesn't have an obvious lifetime in the list of named lifetimes that it should be inferred to, just pick the first one for the diagnostic.

This happens e.g. in

```rust
fn foo<'a, 'b>(a: Struct<'a>, b: Struct<'b>) -> impl Trait<'a, 'b> {
    if bar() { a } else { b }
}
```

where we get a lifetime variable that combines the lifetimes of `a` and `b` creating a lifetime that is the intersection of both. Right now the type system cannot express this and thus we get an error, but that error also can't express this.

I can also create an entirely new diagnostic that mentions all involved lifetimes, so it would actually mention `'a` and `'b` instead of just `'b`.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions