From e604382ad230219f0f692188a6802fd046574444 Mon Sep 17 00:00:00 2001 From: Steve Klabnik Date: Fri, 27 Mar 2015 14:48:13 -0400 Subject: [PATCH] Explain why &self is common Fixes #23748 --- src/doc/trpl/method-syntax.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/doc/trpl/method-syntax.md b/src/doc/trpl/method-syntax.md index 8cb16f7ab33..f7cda400526 100644 --- a/src/doc/trpl/method-syntax.md +++ b/src/doc/trpl/method-syntax.md @@ -51,7 +51,8 @@ You can think of this first parameter as being the `x` in `x.foo()`. The three variants correspond to the three kinds of thing `x` could be: `self` if it's just a value on the stack, `&self` if it's a reference, and `&mut self` if it's a mutable reference. We should default to using `&self`, as it's the most -common. Here's an example of all three variants: +common, as Rustaceans prefer borrowing over taking ownership, and references +over mutable references. Here's an example of all three variants: ```rust struct Circle {