Skip to content

Add long explanation for error E0482 #89710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 12, 2021
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion compiler/rustc_error_codes/src/error_codes.rs
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,7 @@ E0468: include_str!("./error_codes/E0468.md"),
E0469: include_str!("./error_codes/E0469.md"),
E0477: include_str!("./error_codes/E0477.md"),
E0478: include_str!("./error_codes/E0478.md"),
E0482: include_str!("./error_codes/E0482.md"),
E0491: include_str!("./error_codes/E0491.md"),
E0492: include_str!("./error_codes/E0492.md"),
E0493: include_str!("./error_codes/E0493.md"),
Expand Down Expand Up @@ -599,7 +600,6 @@ E0785: include_str!("./error_codes/E0785.md"),
// E0479, // the type `..` (provided as the value of a type parameter) is...
// E0480, // lifetime of method receiver does not outlive the method call
// E0481, // lifetime of function argument does not outlive the function call
E0482, // lifetime of return value does not outlive the function call
// E0483, // lifetime of operand does not outlive the operation
// E0484, // reference is not valid at the time of borrow
// E0485, // automatically reference is not valid at the time of borrow
Expand Down
68 changes: 68 additions & 0 deletions compiler/rustc_error_codes/src/error_codes/E0482.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
A lifetime of return value does not outlive the function call.

Erroneous code example:

```compile_fail,E0482
fn prefix<'a>(
words: impl Iterator<Item = &'a str>
) -> impl Iterator<Item = String> {
words.map(|v| format!("foo-{}", v))
}
```

To fix this error, make the lifetime of the returned value explicit.

```
fn prefix<'a>(
words: impl Iterator<Item = &'a str> + 'a
) -> impl Iterator<Item = String> + 'a {
words.map(|v| format!("foo-{}", v))
}
```

[`impl Trait`] feature in return type have implicit `'static` lifetime
Copy link
Member

@GuillaumeGomez GuillaumeGomez Oct 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[`impl Trait`] feature in return type have implicit `'static` lifetime
The [`impl Trait`] feature uses an implicit `'static` lifetime restriction in the returned type

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed that part and split the sentence in two. I also made it sound different, because before the explanation sounded like all -> impl Trait structures force 'static lifetime in all cases (like Box<Trait>), which is not true according to RFC I believe.

Those can be different lifetimes and only my example required 'static. Please correct me if I'm wrong @GuillaumeGomez or @nagisa.

restriction and the type implementing the `Iterator` passed to the function
lives just `'a`, so shorter time.

The solution involves adding lifetime bound to both function argument and
the return value to make sure that the values inside the iterator
are not dropped when the function goes out of the scope.

Alternative solution would be to guarantee that the `Item` references
in the iterator are alive for the whole lifetime of the program.

```
fn prefix(
words: impl Iterator<Item = &'static str>
) -> impl Iterator<Item = String> {
words.map(|v| format!("foo-{}", v))
}
```

Similar lifetime problem might arise when returning closures.

Erroneous code example:

```compile_fail,E0482
fn foo(x: &mut Vec<i32>) -> impl FnMut(&mut Vec<i32>) -> &[i32] {
|y| {
y.append(x);
y
}
}
```

Analogically, solution here is to use explicit return lifetime
and move the ownership of the variable to the closure.

```
fn foo<'a>(x: &'a mut Vec<i32>) -> impl FnMut(&mut Vec<i32>) -> &[i32] + 'a {
move |y| {
y.append(x);
y
}
}
```

- [`impl Trait`]: https://doc.rust-lang.org/reference/types/impl-trait.html
- [RFC 1951]: https://rust-lang.github.io/rfcs/1951-expand-impl-trait.html
2 changes: 1 addition & 1 deletion src/tools/tidy/src/error_codes_check.rs
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ use regex::Regex;
// A few of those error codes can't be tested but all the others can and *should* be tested!
const EXEMPTED_FROM_TEST: &[&str] = &[
"E0227", "E0279", "E0280", "E0313", "E0377", "E0461", "E0462", "E0464", "E0465", "E0476",
"E0482", "E0514", "E0519", "E0523", "E0554", "E0640", "E0717", "E0729",
"E0514", "E0519", "E0523", "E0554", "E0640", "E0717", "E0729",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

];

// Some error codes don't have any tests apparently...
Expand Down