aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Pike <r@golang.org>2012-09-22 05:55:05 +1000
committerRob Pike <r@golang.org>2012-09-22 05:55:05 +1000
commit0dabae4a85ae96799f3dfe74a0cdc4f1f50c7451 (patch)
treef222003b0a3d34f0eb94546463a69539e62b48b3
parent261565842d4f34cc19645ae46f8946c1f02cff48 (diff)
downloadgo-0dabae4a85ae96799f3dfe74a0cdc4f1f50c7451.tar.gz
go-0dabae4a85ae96799f3dfe74a0cdc4f1f50c7451.zip
[release-branch.go1] faq: go does not have duck typing
««« backport d3d3e0825dd2 faq: go does not have duck typing R=golang-dev, 0xjnml, iant, adonovan, aram CC=golang-dev https://golang.org/cl/6500092 »»»
-rw-r--r--doc/go_faq.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html
index 64acd96a2d..b7fdb7b568 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -541,7 +541,7 @@ Why doesn't Go have "implements" declarations?</h3>
<p>
A Go type satisfies an interface by implementing the methods of that interface,
nothing more. This property allows interfaces to be defined and used without
-having to modify existing code. It enables a kind of "duck typing" that
+having to modify existing code. It enables a kind of structural typing that
promotes separation of concerns and improves code re-use, and makes it easier
to build on patterns that emerge as the code develops.
The semantics of interfaces is one of the main reasons for Go's nimble,