Skip to content

Commit

Permalink
Fix formatting of the pointers guide.
Browse files Browse the repository at this point in the history
  • Loading branch information
ucarion committed Nov 26, 2014
1 parent 0e06f71 commit 6cb03ba
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/doc/guide-pointers.md
Original file line number Diff line number Diff line change
Expand Up @@ -572,7 +572,7 @@ fn add_one(x: &mut int) -> int {
fn main() {
let x = box 5i;
println!("{}", add_one(&*x)); // error: cannot borrow immutable dereference
println!("{}", add_one(&*x)); // error: cannot borrow immutable dereference
// of `&`-pointer as mutable
}
```
Expand Down Expand Up @@ -700,9 +700,9 @@ This gives you flexibility without sacrificing performance.

You may think that this gives us terrible performance: return a value and then
immediately box it up ?! Isn't that the worst of both worlds? Rust is smarter
than that. There is no copy in this code. main allocates enough room for the
`box , passes a pointer to that memory into foo as x, and then foo writes the
value straight into that pointer. This writes the return value directly into
than that. There is no copy in this code. `main` allocates enough room for the
`box`, passes a pointer to that memory into `foo` as `x`, and then `foo` writes
the value straight into that pointer. This writes the return value directly into
the allocated box.

This is important enough that it bears repeating: pointers are not for
Expand Down

0 comments on commit 6cb03ba

Please sign in to comment.