diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-09-03 20:10:07 -0400 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-09-03 20:10:07 -0400 |
| commit | 723ebc2471739cc768630a57b0aa24019725b999 (patch) | |
| tree | 516866ec657f866c79fcd4d3df352eff037cb131 /src/rustllvm/RustWrapper.cpp | |
| parent | b96618e18b3e4f287ec34fc337dfc4c11d813b39 (diff) | |
| parent | 986f523b89924b4ba47daf0beee283a65d26f355 (diff) | |
| download | rust-723ebc2471739cc768630a57b0aa24019725b999.tar.gz rust-723ebc2471739cc768630a57b0aa24019725b999.zip | |
Rollup merge of #28203 - benschulz:book-deref-coercion, r=brson
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.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions