mirror of
https://github.com/golang/go
synced 2024-11-21 21:44:40 -07:00
doc/effective_go.html: remove spurious word
Fixes #6003. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/12387045
This commit is contained in:
parent
af8426eebe
commit
38a77ff03f
@ -2560,7 +2560,7 @@ One place this situation arises is when it is necessary to guarantee within the
|
|||||||
it actually satisfies the interface.
|
it actually satisfies the interface.
|
||||||
If a type—for example,
|
If a type—for example,
|
||||||
<code><a href="/pkg/encoding/json/#RawMessage">json.RawMessage</a></code>—needs
|
<code><a href="/pkg/encoding/json/#RawMessage">json.RawMessage</a></code>—needs
|
||||||
a custom its JSON representation, it should implement
|
a custom JSON representation, it should implement
|
||||||
<code>json.Marshaler</code>, but there are no static conversions that would
|
<code>json.Marshaler</code>, but there are no static conversions that would
|
||||||
cause the compiler to verify this automatically.
|
cause the compiler to verify this automatically.
|
||||||
If the type inadvertently fails to satisfy the interface, the JSON encoder will still work,
|
If the type inadvertently fails to satisfy the interface, the JSON encoder will still work,
|
||||||
|
Loading…
Reference in New Issue
Block a user