diff options
| author | Francesc Campoy <campoy@golang.org> | 2016-01-14 10:14:25 -0800 |
|---|---|---|
| committer | Francesc Campoy Flores <campoy@golang.org> | 2016-01-14 18:22:20 +0000 |
| commit | bb6ca5fe3f1eca133992cdee55d608dd1f0e983c (patch) | |
| tree | 5c517636f90a373d8ffc414c927905025ec87f45 /content/methods.article | |
| parent | c8a14fd7ba16ada15cbd0ee32e1887bf353d0eff (diff) | |
| download | golang-id-tour-bb6ca5fe3f1eca133992cdee55d608dd1f0e983c.tar.xz | |
tour: fix typo
Fixes golang/go#13951
Change-Id: I5c830371f987c114f37344d00a68f4b0735f47eb
Reviewed-on: https://go-review.googlesource.com/18670
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Diffstat (limited to 'content/methods.article')
| -rw-r--r-- | content/methods.article | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/methods.article b/content/methods.article index ec99b7e..67c381e 100644 --- a/content/methods.article +++ b/content/methods.article @@ -134,7 +134,7 @@ This can be more efficient if the receiver is a large struct, for example. In this example, both `Scale` and `Abs` are with receiver type `*Vertex`, even though the `Abs` method needn't modify its receiver. -In general, all methods on a given type to should have either value or pointer +In general, all methods on a given type should have either value or pointer receivers, but not a mixture of both. (We'll see why over the next few pages.) |