user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Distinguish lifetimes and their annotations

Browse source 
Also, emphasize differently.
This commit is contained in:
KillTheMule 2016-10-06 11:15:47 +02:00 • committed by GitHub
parent 2130637301
commit 7f02eb387d
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/doc/book/lifetimes.md
View file

@ -56,7 +56,7 @@ To fix this, we have to make sure that step four never happens after step
three. The ownership system in Rust does this through a concept called
lifetimes, which describe the scope that a reference is valid for.
*Note* It's important to understand that lifetimes are _descriptive_ not _prescriptive_. This means that the lifetimes of references are determined by the code, not by the lifetime annotations. The annotations, however, point out the lifetimes to the compiler in case it can't figure them out by itself.
**Note** It's important to understand that lifetime annotations are _descriptive_ not _prescriptive_. This means that the lifetimes of references are determined by the code, not by the annotations. The annotations, however, point out the lifetimes to the compiler in case it can't figure them out by itself.
When we have a function that takes an argument by reference, we can be
implicit or explicit about the lifetime of the reference: