Duck typing

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In computer programming with object-oriented programming languages, duck typing is a style of typing in which an object's methods and properties determine the valid semantics, rather than its inheritance from a particular class or implementation of an explicit interface. The name of the concept refers to the duck test, attributed to James Whitcomb Riley (see history below), which may be phrased as follows:

When I see a bird that walks like a duck and swims like a duck and quacks like a duck, I call that bird a duck.[1]

In duck typing, a programmer is only concerned with ensuring that objects behave as demanded of them in a given context, rather than ensuring that they are of a specific type. For example, in a non-duck-typed language, one would create a function that requires that the object passed into it be of type Duck, in order to ensure that that function can then use the object's walk and quack methods. In a duck-typed language, the function would take an object of any type and simply call its walk and quack methods, producing a run-time error if they are not defined. Instead of specifying types formally, duck typing practices rely on documentation, clear code, and testing to ensure correct use.

Concept examples[edit]

Consider the following pseudo-code for a duck-typed language:

function calculate(a, b, c) => return (a + b)*c

example1 = calculate (1, 2, 3)
example2 = calculate ([1, 2, 3], [4, 5, 6], 2)
example3 = calculate ('apples ', 'and oranges, ', 3)

print to_string example1
print to_string example2
print to_string example3

In the example, each time the calculate function is called, objects without related inheritance may be used (numbers, lists and strings). As long as the objects support the "+" and "*" methods, the operation will succeed. If translated to Ruby or Python, for example, the result of the code would be:

[1, 2, 3, 4, 5, 6, 1, 2, 3, 4, 5, 6]
apples and oranges, apples and oranges, apples and oranges,

Thus, duck typing can work the same as polymorphism, but without inheritance. The only restriction that function calculate places on its arguments is that they implement the "+" and the "*" methods.

The duck test can be seen in the following example (in Python). As far as the function in_the_forest is concerned, the Person object is a duck:

class Duck:
	def quack(self):
	def feathers(self):
		print("The duck has white and gray feathers.")
class Person:
	def quack(self):
		print("The person imitates a duck.")
	def feathers(self):
		print("The person takes a feather from the ground and shows it.")
	def name(self):
		print("John Smith")
def in_the_forest(duck):
def game():
	donald = Duck()
	john = Person()

In statically typed languages[edit]

Certain usually statically typed languages such as Boo and the version 4 release of C# have extra type annotations[2][3] that instruct the compiler to arrange for type checking of classes to occur at run-time rather than compile time, and include run-time type checking code in the compiled output.

Other statically typed languages like F#, and C++ (by the use of templates) support static duck typing, where the type is verified to have the specific method signatures during compilation.

Comparison with other type systems[edit]

Structural type systems[edit]

Duck typing is similar to, but distinct from structural typing. Structural typing is a static typing system that determines type compatibility and equivalence by a type's structure, whereas duck typing is dynamic and determines type compatibility by only that part of a type's structure that is accessed during run time.

The OCaml, Scala, and Go languages use structural type systems.

Protocols and Interfaces[edit]

Protocols and interfaces can provide some of the benefits of duck typing, but duck typing is distinct in that no explicit interface is defined. For example, if a third party Java library implements a class you are not allowed to modify, you cannot use an instance of the class in place of an interface you have defined yourself, whereas duck typing would allow this. Again, all of an interface must be satisfied for compatibility.

Templates or generic types[edit]

Template, or generic functions or methods apply the duck test in a static typing context; this brings all the advantages and disadvantages of static versus dynamic type checking in general. Duck typing can also be more flexible in that only the methods actually called at run time need to be implemented, while templates require implementation of all methods that cannot be proven unreachable at compile time.

Examples include the languages C++ and D with templates, which developed from Ada generics.


One issue with duck typing is that it forces programmers to have a much wider understanding of the code they are working with at any given time. For instance, in Python, one could easily create a class called Wine, which expects a class implementing the "press" attribute as an ingredient. However, a class called Trousers might also implement the press() method. With duck typing, in order to prevent strange, hard-to-detect errors, the developer needs to be aware of each potential use of the method "press", even when it's conceptually unrelated to what they are working on. By way of contrast, in a strongly and statically typed language that uses type hierarchies and parameter type checking, it's much harder to supply an unexpected object type to a class. For example, in a language like Java, the ambiguity in the above reuse of the method name press() would not be a problem unless one of the two classes was deliberately defined as a child of the other.

Proponents of duck typing, such as Guido van Rossum, argue that the issue is handled by testing, and the necessary knowledge of the codebase required to maintain it.[4][5]

Criticisms around duck typing tend to be special cases of broader points of contention regarding dynamically typed versus statically typed programming language semantics.


Alex Martelli made an early (2000) use of the term in a message to the comp.lang.python newsgroup:

In other words, don't check whether it IS-a duck: check whether it QUACKS-like-a duck, WALKS-like-a duck, etc, etc, depending on exactly what subset of duck-like behaviour you need to play your language-games with.


In C#[edit]

In C# 4.0 the compiler and runtime collaborate to implement dynamic member lookup. Parameter duck is declared dynamic in method InTheForest of class Program.

using System;
namespace DuckTyping
	public class Duck
		public void Quack()	{ Console.WriteLine("Quaaaaaack!"); }
		public void Feathers() { Console.WriteLine("The duck has white and gray feathers."); }
	public class Person
		public void Quack()	{ Console.WriteLine("The person imitates a duck."); }
		public void Feathers()
			Console.WriteLine("The person takes a feather from the ground and shows it.");
	internal class Program
		private static void InTheForest(dynamic duck)
		private static void Game()
			Duck donald = new Duck();
			Person john = new Person();
		private static void Main()

In CFML[edit]

The web application scripting language CFML allows function arguments to be specified as having type any. For this sort of argument, an arbitrary object can be passed in and method calls are bound dynamically at runtime. If an object does not implement a called method, a runtime exception is thrown that can be caught and handled gracefully. In ColdFusion 8, this can be picked up as a defined event onMissingMethod() rather than through an exception handler. An alternative argument type of WEB-INF.cftags.component restricts the passed argument to be a ColdFusion Component (CFC), which provides better error messages should a non-object be passed in.

Other CFML application servers such as Lucee work analogously to ColdFusion's CFML implementation.

In Dart[edit]

class Duck {
	quack() => print("Quack, quack!");
	fly()	 => print("Flap, Flap!");
class Person {
	quack() => print("I'm Quackin'!");
	fly()	 => print("I'm Flyin'!");
inTheForest(mallard) {
main() {
	inTheForest(new Duck());
	inTheForest(new Person());

In Cobra[edit]

In addition to static typing, Cobra allows one to declare objects of type 'dynamic' and send any message to them. At run-time the message passing will either succeed or throw an exception. The 'dynamic' type is the default for object variables and method arguments when a type has not been explicitly declared for them. This feature was inspired by Objective-C.[6]

In Common Lisp[edit]

Common Lisp includes an object-oriented system (Common Lisp Object System, or shorter CLOS) providing classes with multiple inheritance and generic functions that can specialize on multiple arguments. The combination of CLOS and Lisp's dynamic typing make duck typing a common programming style in Common Lisp.

With Common Lisp one also does not need to query the types, since at runtime an error will be signaled when a generic function is not applicable. The error can be handled with the Condition System of Common Lisp. Methods are defined outside of classes and can also be defined for specific objects.

;; We describe a protocol for 'duck-like' objects. Objects with methods for
;; these three generic functions may be considered 'ducks', for all intents
;; and purposes -- regardless of their superclass.
(defgeneric quack (something))
(defgeneric feathers (something))
;; Implementation of the protocol for class DUCK.
(defclass duck () ())
(defmethod quack ((a-duck duck))
	(print "Quaaaaaack!"))
(defmethod feathers ((a-duck duck))
	(print "The duck has white and gray feathers."))
;; But we can also implement it for PERSON, without inheriting from DUCK.
(defclass person () ())
(defmethod quack ((a-person person))
	(print "The person imitates a duck."))
(defmethod feathers ((a-person person))
	(print "The person takes a feather from the ground and shows it."))
;; IN-THE-FOREST does not need to be polymorphic. Its 'duck' argument is
;; anything that implements the duck protocol above.
(defun in-the-forest (duck)
	(quack duck)
	(feathers duck))
;; GAME can also just be a regular function.
(defun game ()
	(let ((donald (make-instance 'duck))
		(john (make-instance 'person)))
	(in-the-forest donald)
	(in-the-forest john)))

The usual development style of Common Lisp (by using a Lisp REPL like SLIME) allows also the interactive repair:

? (defclass cat () ())
? (quack (make-instance 'cat))
> Error: There is no applicable method for the generic function:
>    when called with arguments:
>      (#<CAT #x300041C7EEFD>)
> If continued: Try calling it again
1 > (defmethod quack ((a-cat cat))

(print "The cat imitates a duck."))

1 > (continue)
"The cat imitates a duck."

This way software can be developed by extending partially working duck typed code.

In Groovy[edit]

In Groovy, the Java-derived scripting language, the above Java example can be greatly simplified, because Groovy uses duck typing by default when calling a method.

class Duck
	def walk() { println "I'm a Duck, I can walk..." }
	def swim() { println "I'm a Duck, I can swim..." }
	def quack() { println "I'm a Duck, I can quack" }
class Person
	def walk() { println "I'm a Person, I can walk..." }
	def swim() { println "I'm a Person, I can swim..." }
	def talk() { println "I'm a Person, I can talk..." }
def d = new Duck()
def p = new Person()
d.walk()	// Ok, duck has walk() method
d.swim()	// Ok, duck has swim() method
d.quack()	// Ok, duck has quack() method
p.walk()	// Ok, person has walk() method
p.swim()	// Ok, person has swim() method
p.quack()	// Runtime error, no quack() method

In Java[edit]

In Java duck typing may be achieved with reflection.

import java.lang.reflect.InvocationHandler;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;
import java.lang.reflect.Proxy;
public class DuckTyping {
	interface Walkable	{ void walk(); }
	interface Swimmable { void swim(); }
	interface Quackable { void quack(); }
	public static void main(String[] args) {
		Duck d = new Duck();
		Person p = new Person();
		as(Walkable.class, d).walk();	//OK, duck has walk() method
		as(Swimmable.class, d).swim();	//OK, duck has swim() method
		as(Quackable.class, d).quack(); //OK, duck has quack() method
		as(Walkable.class, p).walk();	//OK, person has walk() method
		as(Swimmable.class, p).swim();	//OK, person has swim() method
		as(Quackable.class, p).quack(); //Runtime Error, person does not have quack() method
	static <T> T as(Class<T> t, final Object obj) {
		return (T) Proxy.newProxyInstance(t.getClassLoader(), new Class[] {t},
			new InvocationHandler() {
				public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
					try {
						return obj.getClass()
							.getMethod(method.getName(), method.getParameterTypes())
							.invoke(obj, args);
					} catch (NoSuchMethodException nsme) {
						throw new NoSuchMethodError(nsme.getMessage());
					} catch (InvocationTargetException ite) {
						throw ite.getTargetException();
class Duck {
	public void walk()	{System.out.println("I'm Duck, I can walk...");}
	public void swim()	{System.out.println("I'm Duck, I can swim...");}
	public void quack() {System.out.println("I'm Duck, I can quack...");}
class Person {
	public void walk()	{System.out.println("I'm Person, I can walk...");}
	public void swim()	{System.out.println("I'm Person, I can swim...");}
	public void talk()	{System.out.println("I'm Person, I can talk...");}

In JavaScript[edit]

var Duck = function() {
	this.quack = function() {alert('Quaaaaaack!');};
	this.feathers = function() {alert('The duck has white and gray feathers.');};
	return this;
var Person = function() {
	this.quack = function() {alert('The person imitates a duck.');};
	this.feathers = function() {alert('The person takes a feather from the ground and shows it.');}; = function() {alert('John Smith');};
	return this;
var inTheForest = function(duck) {
var game = function() {
	var donald = new Duck();
	var john = new Person();

In Lua[edit]

Lua supports duck typing as part of the Metatable weak-typing system. Any reference to a table's member function is checked dynamically at run-time. If an object does not implement the requested function, a run-time error is produced. If a data member is requested, but does not exist, a nil value is returned.

local duck_mt = {}
local duck_methods = {}
duck_mt.__index = duck_methods
function duck_methods:quack()
	print "Quaaaaaack!"
function duck_methods:feathers()
	return "The duck has white and gray feathers."
local function new_duck()
	return setmetatable({}, duck_mt)
local person_mt = {}
local person_methods = {}
person_mt.__index = person_methods
function person_methods:quack()
	print "The person imitates a duck."
function person_methods:feathers()
	return "The person takes a feather from the ground and shows it."
function person_methods:get_name()
	return self.firstname .. " " .. self.lastname
local function new_person(t)
	return setmetatable(t or {}, person_mt)
local function in_the_forest(duck)
local donald = new_duck()
local john = new_person {firstname="John", lastname="Smith"}

In Objective-C[edit]

Objective-C, a cross between C and Smalltalk, allows one to declare objects of type 'id' and send any message to them (provided the method is declared somewhere), like in Smalltalk. The sender can test an object to see, if it responds to a message, the object can decide at the time of the message whether it will respond to it or not, and, if the sender sends a message a recipient cannot respond to, an exception is raised. Thus, duck typing is fully supported by Objective-C.

#import <Foundation/Foundation.h>
@interface Duck : NSObject
- (void)quack;
@implementation Duck
- (void)quack { NSLog(@"Quaaaack!"); }
@interface Person : NSObject
- (void)quack;
@implementation Person
- (void)quack { NSLog(@"The person imitates a duck."); }
@interface Dog : NSObject
- (void)bark;
@implementation Dog
- (void)bark { NSLog(@"Baaaaark!"); }
void inTheForest(id duck) {
	if ([duck respondsToSelector:@selector(quack)]) {
		[duck quack];
int main(int argc, const char * argv[]) {
	@autoreleasepool {
		inTheForest([[Duck alloc] init]);
		inTheForest([[Person alloc] init]);
		inTheForest([[Dog alloc] init]);
	return 0;

In Perl[edit]

Perl looks for method definitions in package set with bless function.

use strict;
package Duck;
sub hatch {
	bless \(my $self), shift;
sub quack {
	print "Quaaaaaack!\n";
sub feathers {
	print "The duck has white and gray feathers.\n";
package Person;
sub accept_birth {
	bless \(my $self), shift;
sub quack {
	print "The person imitates a duck.\n";
sub feathers {
	print "The person takes a feather from the ground and shows it.\n";
package main;
sub in_the_forest
	my $duck = shift;
my $duck = Duck->hatch();
my $person = Person->accept_birth();
in_the_forest( $duck );
in_the_forest( $person );


The duck has white and gray feathers.
The person imitates a duck.
The person takes a feather from the ground and shows it.

In PHP[edit]

PHP leans towards the Java convention of using inheritance and the user land type system (type hinting method arguments or using instanceof class or interface) in favour of duck typing. Below is an example of duck typing:

class Duck {
	function quack() { echo "Quack", PHP_EOL; }
	function fly() { echo "Flap, Flap", PHP_EOL; }
class Person {
	function quack() { echo "I try to imitate a duck quack", PHP_EOL; }
	function fly() { echo "I take an airplane", PHP_EOL; }
function in_the_forest($object) {
in_the_forest(new Duck);
in_the_forest(new Person);


Flap, Flap
I try to imitate a duck quack
I take an airplane

In PowerShell[edit]

This is the concept example from the beginning of the page.

Function calculate($a, $b, $c) {
	return ($a + $b)*$c
calculate 1 2 3
"$(calculate (1, 2, 3) (4, 5, 6) 2)"
calculate 'apples ' 'and oranges, ' 3

In Python[edit]

Duck typing is heavily used in Python, with the canonical example being file-like classes (for example, cStringIO allows a Python string to be treated as a file).

class Duck:
	def quack(self):
		print "Quack, quack!"
	def fly(self):
		print "Flap, Flap!"
class Person:
	def quack(self):
		print "I'm Quackin'!"
	def fly(self):
		print "I'm Flyin'!"
def in_the_forest(mallard):


Quack, quack!
Flap, Flap!
I'm Quackin'!
I'm Flyin'!

According to the EAFP principle, instead of checking to see, if some purportedly Duck-like object has a quack() method (using if hasattr(mallard, "quack"): ...) it's usually preferable to wrap the attempted quack with proper exception handling:

except (AttributeError, TypeError):
	print("mallard can't quack()")

or, a more common use of the principle is to just let the exception "bubble up", that is, to let the exception be raised, and let whatever function or method called the code in question to deal with it (or, if nothing deals with it, to let the exception be raised to the user). This gives better feedback on bad input, and avoids masking bugs.

In Ruby[edit]

class Duck
	def quack
	puts "Quaaaaaack!"
	def feathers
	puts "The duck has white and gray feathers."
class Person
	def quack
	puts "The person imitates a duck."
	def feathers
	puts "The person takes a feather from the ground and shows it."
def in_the_forest(duck)
def game
	donald =
	john =
	in_the_forest donald
	in_the_forest john


The duck has white and gray feathers.
The person imitates a duck.
The person takes a feather from the ground and shows it.

In Smalltalk[edit]

Duck typing is fundamental to Smalltalk. Variables have no data type, and can hold any object. Behavior is triggered by messages sent between objects. Any arbitrary string can be sent to any object as a message. The receiving object checks its method list for a matching behavior. This is the only approximation of type-checking in the language.

Moreover, a message with no matching method is not necessarily an error. In this case, the receiving object triggers its own doesNotUnderstand: method, inherited from Object. The default implementation raises an error, but this can be overridden to perform arbitrary operations based on the original message.


  1. ^ Heim, Michael (2007). Exploring Indiana Highways. Exploring America's Highway. p. 68. ISBN 978-0-9744358-3-1. 
  2. ^ Boo: Duck Typing
  3. ^ Anders Hejlsberg Introduces C# 4.0 at PDC 2008
  4. ^ Bruce Eckel. "Strong Typing vs. Strong Testing". mindview. 
  5. ^ Bill Venners. "Contracts in Python. A Conversation with Guido van Rossum, Part IV". Artima. 
  6. ^ "Cobra - Acknowledgements". Retrieved 2010-04-07. 

External links[edit]