OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Remove rule that is confusing

Browse Source 
The original text stated that one should only return a unique or managed pointer if you were given one in the first place. This makes it sound as if the function *should* return a unique pointer if it were given a unique pointer. The rest of the section goes on to describe why this is bad, and the example of bad code does exactly what the rule just said to do.

I reworded the original rule into a reference to the more concise rule mentioned at the bottom of the section, which helps add emphasis (a la 'it bears repeating').
This commit is contained in:
Brandon Waskiewicz 2014-04-17 16:59:58 -04:00
parent ff0b0d5cee
commit 58ae1e7c62
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/doc/guide-pointers.md
View File

@ -430,8 +430,9 @@ great detail, so if you want the full details, check that out.
# Returning Pointers # Returning Pointers
We've talked a lot about functions that accept various kinds of pointers, but We've talked a lot about functions that accept various kinds of pointers, but
what about returning them? Here's the rule of thumb: only return a unique or what about returning them? In general, it is better to let the caller decide
managed pointer if you were given one in the first place. how to use a function's output, instead of assuming a certain type of pointer
is best.
What does that mean? Don't do this: What does that mean? Don't do this: