rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2025-04-23 16:12:47 +02:00
Code Issues Releases Activity

Update lifetimes-function-calls.md (#223)

Browse Source 
* Update lifetimes-function-calls.md

I am trying to describe the problem lifetimes solve. It may seem they are complex and useless, but the paragraph starts from the problem Rust cannot
solve on it's own (yet). Then the paragraph illustrates the problem represented in the code and how lifetimes solve it.

* Update lifetimes-function-calls.md

Moving the generic explanation of why lifetimes are important to the speaker notes.

* Make language more direct

Co-authored-by: Martin Geisler <martin@geisler.net>
This commit is contained in:
Igor Petruk 2023-01-24 08:50:05 +00:00 committed by GitHub
parent 7f178d6212
commit 4444e9a078
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/ownership/lifetimes-function-calls.md
View File

@ -50,5 +50,11 @@ In the above example, try the following:
Note how this does not compile since `p3` outlives `p2`.
* Reset the workspace and change the function signature to `fn left_most<'a, 'b>(p1: &'a Point, p2: &'a Point) -> &'b Point`. This will not compile because the relationship between the lifetimes `'a` and `'b` is unclear.
* Another way to explain it:
* Two references to two values are borrowed by a function and the function returns
another reference.
* It must have come from one of those two inputs (or from a global variable).
* Which one is it? The compiler needs to to know, so at the call site the returned reference is not used
for longer than a variable from where the reference came from.
</details>