diff options
| author | bors <bors@rust-lang.org> | 2014-06-05 20:16:53 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-06-05 20:16:53 -0700 |
| commit | ae9577052d99203806fd83c84669d25fbe0af367 (patch) | |
| tree | 2e55f0103384d91e70d0f5f958068c59c24a0e14 | |
| parent | e14bc6698a8d7f961e3205c94184396f539062bd (diff) | |
| parent | 7e0cc34d629937e739ebf4404e5fe99c70d4b364 (diff) | |
auto merge of #14664 : reem/rust/lifetimes-guide-grammar, r=brson
Removed strange fragment-like thing in the intro.
| -rw-r--r-- | src/doc/guide-lifetimes.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/guide-lifetimes.md b/src/doc/guide-lifetimes.md index 2f519306dfd..65f37031674 100644 --- a/src/doc/guide-lifetimes.md +++ b/src/doc/guide-lifetimes.md @@ -14,9 +14,9 @@ Despite their complete safety, a reference's representation at runtime is the same as that of an ordinary pointer in a C program. They introduce zero overhead. The compiler does all safety checks at compile time. -Although references have rather elaborate theoretical underpinnings usually -introduced as (e.g. region pointers), the core concepts will be familiar to -anyone who has worked with C or C++. The best way to explain how they are +Although references have rather elaborate theoretical underpinnings +(e.g. region pointers), the core concepts will be familiar to anyone +who has worked with C or C++. The best way to explain how they are used—and their limitations—is probably just to work through several examples. # By example |
