about summary refs log tree commit diff
diff options
context:
space:
mode:
-rw-r--r--src/doc/guide-pointers.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/src/doc/guide-pointers.md b/src/doc/guide-pointers.md
index 5c6c562b72d..9780a12a402 100644
--- a/src/doc/guide-pointers.md
+++ b/src/doc/guide-pointers.md
@@ -430,8 +430,9 @@ great detail, so if you want the full details, check that out.
 # Returning Pointers
 
 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
-managed pointer if you were given one in the first place.
+what about returning them? In general, it is better to let the caller decide
+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: