From 0dabae4a85ae96799f3dfe74a0cdc4f1f50c7451 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Sat, 22 Sep 2012 05:55:05 +1000 Subject: [PATCH] [release-branch.go1] faq: go does not have duck typing MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit ««« backport d3d3e0825dd2 faq: go does not have duck typing R=golang-dev, 0xjnml, iant, adonovan, aram CC=golang-dev https://golang.org/cl/6500092 »»» --- doc/go_faq.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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, -- 2.50.0