-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto merge of #94453 - matthiaskrgr:rollup-xv9y98j, r=matthiaskrgr
Rollup of 6 pull requests Successful merges: - #92399 (fix typo in btree/vec doc: Self -> self) - #92823 (Tweak diagnostics) - #94248 (Fix ICE when passing block to while-loop condition) - #94414 (Fix ICE when using Box<T, A> with large A) - #94445 (4 - Make more use of `let_chains`) - #94449 (Add long explanation for E0726) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
- Loading branch information
Showing
47 changed files
with
591 additions
and
321 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
An argument lifetime was elided in an async function. | ||
|
||
Erroneous code example: | ||
|
||
When a struct or a type is bound/declared with a lifetime it is important for | ||
the Rust compiler to know, on usage, the lifespan of the type. When the | ||
lifetime is not explicitly mentioned and the Rust Compiler cannot determine | ||
the lifetime of your type, the following error occurs. | ||
|
||
```compile_fail,E0726 | ||
use futures::executor::block_on; | ||
struct Content<'a> { | ||
title: &'a str, | ||
body: &'a str, | ||
} | ||
async fn create(content: Content) { // error: implicit elided | ||
// lifetime not allowed here | ||
println!("title: {}", content.title); | ||
println!("body: {}", content.body); | ||
} | ||
let content = Content { title: "Rust", body: "is great!" }; | ||
let future = create(content); | ||
block_on(future); | ||
``` | ||
|
||
Specify desired lifetime of parameter `content` or indicate the anonymous | ||
lifetime like `content: Content<'_>`. The anonymous lifetime tells the Rust | ||
compiler that `content` is only needed until create function is done with | ||
it's execution. | ||
|
||
The `implicit elision` meaning the omission of suggested lifetime that is | ||
`pub async fn create<'a>(content: Content<'a>) {}` is not allowed here as | ||
lifetime of the `content` can differ from current context: | ||
|
||
```ignore (needs futures dependency) | ||
async fn create(content: Content<'_>) { // ok! | ||
println!("title: {}", content.title); | ||
println!("body: {}", content.body); | ||
} | ||
``` | ||
|
||
Know more about lifetime elision in this [chapter][lifetime-elision] and a | ||
chapter on lifetimes can be found [here][lifetimes]. | ||
|
||
[lifetime-elision]: https://doc.rust-lang.org/book/ch10-03-lifetime-syntax.html#lifetime-elision | ||
[lifetimes]: https://doc.rust-lang.org/rust-by-example/scope/lifetime.html |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.