From: Rob Pike Date: Fri, 21 Sep 2012 19:55:05 +0000 (+1000) Subject: [release-branch.go1] faq: go does not have duck typing X-Git-Tag: go1.0.3~33 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=0dabae4a85ae96799f3dfe74a0cdc4f1f50c7451;p=gostls13.git [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 »»» --- 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?

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,