Duck typing mental model in TypeScript - Step-by-Step Execution

Concept Flow - Duck typing mental model in TypeScript

Start with an object

↓

Check if object has required properties

Yes↓

Treat object as that type

↓

Use object with expected methods/properties

↓

End

Duck typing means if an object has the right properties, TypeScript treats it as that type without explicit inheritance.

Execution Sample

Typescript

interface Quackable {
  quack(): void;
}

function makeItQuack(obj: Quackable) {
  obj.quack();
}

const duck = { quack: () => console.log('Quack!') };
makeItQuack(duck);

This code shows that an object with a quack method can be used where Quackable is expected.

Execution Table

Step	Action	Object Properties Checked	Result	Output
1	Call makeItQuack with duck	duck has quack method	Passes type check
2	Inside makeItQuack, call obj.quack()	N/A	Method called	Quack!
3	Function ends	N/A	Execution complete

💡 Function ends after calling quack method on object that matches interface shape

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
duck	{ quack: function }	{ quack: function }	{ quack: function }	{ quack: function }
obj	undefined	{ quack: function }	{ quack: function }	{ quack: function }

Key Moments - 2 Insights

Why does TypeScript accept the duck object without explicitly implementing Quackable?

Because TypeScript uses duck typing, it checks if the object has the required properties (here, quack method) rather than requiring explicit interface implementation, as shown in execution_table step 1.

What happens if the object lacks the quack method?

TypeScript will give a type error at the call site because the object does not match the expected shape, preventing the function call, unlike the successful call shown in execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the output at step 2?

A No output

B Quack!

C Error: quack is not a function

D undefined

💡 Hint

Check the Output column at step 2 in the execution_table.

At which step does TypeScript confirm the object matches the expected type?

A Step 1

B Step 2

C Step 3

D Before Step 1

💡 Hint

Look at the Result column in execution_table step 1.

If the duck object lacked the quack method, what would change in the execution table?

A Step 3 would be skipped but step 2 runs

B Step 2 would output 'Quack!' anyway

C Step 1 would show a type error and no further steps occur

D No change, code runs as normal

💡 Hint

Refer to key_moments about missing properties causing type errors before function execution.

Concept Snapshot

Duck typing in TypeScript means an object is accepted if it has the required properties.
No need for explicit interface implementation.
TypeScript checks shape, not inheritance.
If object matches shape, it can be used as that type.
Missing properties cause type errors at compile time.

Full Transcript

Duck typing in TypeScript means that if an object has the right properties and methods, TypeScript treats it as that type without needing explicit inheritance or interface implementation. In the example, the function makeItQuack expects an object with a quack method. The duck object has a quack method, so TypeScript allows it. When makeItQuack is called with duck, it calls duck.quack(), which prints 'Quack!'. If the object did not have the quack method, TypeScript would give a type error before running the code. This shows how TypeScript uses the shape of objects to check types, not their explicit declarations.

Practice

1. What does duck typing mean in TypeScript?

easy

A. Only objects created from the same class are compatible.

B. If an object has the required properties or methods, it is accepted regardless of its explicit type.

C. TypeScript requires explicit class inheritance to match types.

D. TypeScript checks the runtime type of objects strictly.

Solution

1. Step 1: Understand duck typing concept

   Duck typing means an object is accepted if it has the needed properties or methods, regardless of its declared type.

2. Step 2: Compare with other options

   The other options describe strict or class-based typing, which is not how TypeScript works.

3. Final Answer:

   If an object has the required properties or methods, it is accepted regardless of its explicit type. -> Option B

4. Quick Check:

   Duck typing = structural compatibility [OK]

Hint: Focus on properties, not explicit types, for duck typing [OK]

Common Mistakes:

• Thinking TypeScript requires class inheritance
• Confusing runtime type checks with compile-time checks
• Assuming exact type names must match

2. Which of the following is a correct TypeScript syntax to define a type that matches any object with a name string property and a quack() method returning void?

easy

A. type Duck = { name: string; quack: () => void; };

B. interface Duck { name: string; quack: void; }

C. type Duck = { name: string; quack(): string; };

D. interface Duck { name: string; quack: () => string; }

Solution

1. Step 1: Check property and method types

   The name property must be a string, and quack must be a method returning void.

2. Step 2: Validate each option

   type Duck = { name: string; quack: () => void; }; correctly defines quack as a function returning void. The other options have incorrect method signatures or return types.

3. Final Answer:

   type Duck = { name: string; quack: () => void; }; -> Option A

4. Quick Check:

   Correct method signature = type Duck = { name: string; quack: () => void; }; [OK]

Hint: Method type must be a function signature with correct return type [OK]

Common Mistakes:

• Using method return type as property type
• Confusing void and string return types
• Incorrect interface method syntax

3. What will be the output of this TypeScript code?

interface Duck { name: string; quack: () => void; }

function makeItQuack(duck: Duck) {
  duck.quack();
}

const obj = { name: 'Daffy', quack: () => console.log('Quack!'), swim: () => console.log('Swim') };
makeItQuack(obj);

medium

A. No output

B. Swim

C. Error: obj does not match Duck interface

D. Quack!

Solution

1. Step 1: Check if obj matches Duck interface

   obj has name (string) and quack (function returning void), so it matches by duck typing.

2. Step 2: Call makeItQuack with obj

   Calling duck.quack() runs console.log('Quack!'), printing "Quack!".

3. Final Answer:

   Quack! -> Option D

4. Quick Check:

   Duck typing allows extra properties, output = Quack! [OK]

Hint: Extra properties don't block duck typing; focus on required ones [OK]

Common Mistakes:

• Thinking extra properties cause errors
• Expecting 'Swim' output instead of 'Quack!'
• Assuming runtime type errors

4. Identify the error in this TypeScript code using duck typing:

interface Duck { name: string; quack: () => void; }

const notADuck = { name: 'Donald' };

function makeItQuack(duck: Duck) {
  duck.quack();
}

makeItQuack(notADuck);

medium

A. notADuck is missing the quack method required by Duck interface.

B. The name property should be a number, not a string.

C. makeItQuack should accept any object without type restrictions.

D. There is no error; code runs fine.

Solution

1. Step 1: Check properties of notADuck

   notADuck has name but lacks quack method required by Duck interface.

2. Step 2: Understand TypeScript type checking

   TypeScript will report an error because notADuck does not satisfy the Duck type.

3. Final Answer:

   notADuck is missing the quack method required by Duck interface. -> Option A

4. Quick Check:

   Missing required method = Type error [OK]

Hint: Check all required properties/methods exist for the type [OK]

Common Mistakes:

• Ignoring missing methods in objects
• Assuming extra properties cause errors
• Thinking TypeScript allows missing required members

5. Given this code, which object will TypeScript accept as a valid Duck type?

interface Duck { name: string; quack: () => void; }

const a = { name: 'Daisy', quack: () => console.log('Quack!') };
const b = { name: 'Goose', quack: 'loud' };
const c = { name: 'Swan', quack: () => 'quack' };
const d = { name: 'Mallard' };

function testDuck(duck: Duck) { duck.quack(); }

Which call to testDuck will NOT cause a TypeScript error?

hard

A. testDuck(c);

B. testDuck(b);

C. testDuck(a);

D. testDuck(d);

Solution

1. Step 1: Check each object's quack property type

   a.quack is a function returning void (correct). b.quack is a string (wrong). c.quack is a function returning string (wrong return type). d.quack is missing (wrong).

2. Step 2: Determine which matches Duck interface

   Only object a matches the Duck interface exactly.

3. Final Answer:

   testDuck(a); -> Option C

4. Quick Check:

   Correct method signature only in a [OK]

Hint: Method must be function returning void to match Duck [OK]

Common Mistakes:

• Accepting string or wrong return type as method
• Ignoring missing methods
• Confusing method return types