Take method invocation semantics out of chapter on deref coercion.

[benschulz]

I have two issues with the section "Deref and method calls" of the book's chapter "Deref coercions".

• (Minor) It says "In other words, these are the same two things in Rust:", followed by a code block in which no two things seem similar, much less the same. Presumably this sentence made more sense in a previous revision.
• The next paragraph conflates two concepts which, imho, should kept separate. They are
  • deref coercion, i.e. inserting as many * as necessary and
  • implicitly referencing the receiver, i.e. inserting a single & to satisfy the method's self parameter type.

I appreciate that with the proposed changes the example becomes very contrived, even for a foo-bar-baz one. However, the current exmplanation is just wrong.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[brson]

@bors r+ rollup

Thanks!

[bors]

📌 Commit 986f523 has been approved by brson