Why typed functions matter in Typescript - Visual Breakdown

Concept Flow - Why typed functions matter

Define function with types

↓

Call function with arguments

↓

TypeScript checks argument types

↓

If types match -> function runs

↓

If types mismatch -> error shown

↓

Output or error

This flow shows how TypeScript checks function argument types before running the function, preventing errors.

Execution Sample

Typescript

function add(a: number, b: number): number {
  return a + b;
}

add(2, 3); // valid
add('2', 3); // error

This code defines a typed function and shows a valid call and an invalid call causing a type error.

Execution Table

Step	Action	Arguments	Type Check Result	Function Output / Error
1	Call add with (2, 3)	a=2 (number), b=3 (number)	Types match	Returns 5
2	Call add with ('2', 3)	a='2' (string), b=3 (number)	Type mismatch on a	Error: Argument of type 'string' is not assignable to parameter of type 'number'

💡 Execution stops on error at step 2 due to type mismatch.

Variable Tracker

Variable	Start	After Step 1	After Step 2
a	undefined	2	Error - no value
b	undefined	3	Error - no value
result	undefined	5	No result due to error

Key Moments - 2 Insights

Why does the second call to add cause an error?

Because the argument '2' is a string, but the function expects a number type for parameter 'a' as shown in execution_table step 2.

What happens if types match in a function call?

The function runs normally and returns the expected output, as seen in execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the output of add(2, 3)?

A '23'

B 5

C Error

D undefined

💡 Hint

Check step 1 in the execution_table where types match and output is shown.

At which step does the type error occur?

A Step 2

B No error

C Step 1

D Before step 1

💡 Hint

See execution_table step 2 where the type mismatch is reported.

If we change the function parameter 'a' to type string, what happens to add('2', 3)?

A Returns 5

B Still errors

C It runs without error

D Returns '23'

💡 Hint

Think about type matching in execution_table and how changing parameter types affects calls.

Concept Snapshot

Typed functions in TypeScript:
- Define parameter and return types explicitly
- TypeScript checks arguments at call time
- Mismatched types cause compile-time errors
- Helps catch bugs early
- Ensures function inputs and outputs are predictable

Full Transcript

This visual trace shows why typed functions matter in TypeScript. When you define a function with types, TypeScript checks the types of arguments each time you call it. If the types match, the function runs and returns the expected result. If they don't match, TypeScript shows an error before running the code. This helps catch mistakes early and makes your code safer and easier to understand.

Practice

1. Why is it important to specify types for function parameters and return values in TypeScript?

easy

A. It helps catch errors early by ensuring correct input and output types.

B. It makes the code run faster at runtime.

C. It allows functions to run without any input.

D. It automatically fixes bugs in the code.

Solution

1. Step 1: Understand the role of typed functions

   Typed functions define what types of inputs they accept and what type they return, helping the developer know how to use them correctly.

2. Step 2: Recognize the benefit of early error detection

   By specifying types, TypeScript can catch mistakes before running the code, preventing bugs caused by wrong data types.

3. Final Answer:

   It helps catch errors early by ensuring correct input and output types. -> Option A

4. Quick Check:

   Typed functions = early error detection [OK]

Hint: Typed functions catch type mistakes before running code [OK]

Common Mistakes:

• Thinking types speed up runtime
• Believing typed functions fix bugs automatically
• Assuming functions don't need inputs

2. Which of the following is the correct way to type a function in TypeScript that takes a number and returns a string?

easy

A. function convert(num: number) { return num.toString(); }

B. function convert(num: number): string { return num.toString(); }

C. function convert(num: string): number { return num.length; }

D. function convert(num): string { return num.toString(); }

Solution

1. Step 1: Check parameter and return types

   The function should accept a number parameter and return a string, so the parameter must be typed as number and the return type as string.

2. Step 2: Identify the correct syntax

   function convert(num: number): string { return num.toString(); } correctly types the parameter as number and the return type as string. function convert(num): string { return num.toString(); } misses parameter type, C swaps types, and A misses return type.

3. Final Answer:

   function convert(num: number): string { return num.toString(); } -> Option B

4. Quick Check:

   Parameter: number, Return: string = function convert(num: number): string { return num.toString(); } [OK]

Hint: Parameter and return types must match function purpose [OK]

Common Mistakes:

• Omitting parameter types
• Swapping parameter and return types
• Not specifying return type

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

function add(a: number, b: number): number {
  return a + b;
}

const result = add(5, 10);
console.log(result);

medium

A. 15

B. 510

C. undefined

D. Error: Type mismatch

Solution

1. Step 1: Analyze function parameters and return

   The function add takes two numbers and returns their sum as a number.

2. Step 2: Calculate the result of add(5, 10)

   Adding 5 and 10 gives 15, so result is 15 and console.log prints 15.

3. Final Answer:

   15 -> Option A

4. Quick Check:

   5 + 10 = 15 [OK]

Hint: Add numbers to get sum, not string concat [OK]

Common Mistakes:

• Thinking numbers concatenate as strings
• Expecting undefined return
• Assuming type error without mismatch

4. Identify the error in this TypeScript function and choose the fix:

function greet(name: string): string {
  return 'Hello, ' + name;
}

greet(42);

medium

A. Remove the return type to fix the error.

B. Change function parameter to number: greet(name: number).

C. No error, code runs fine.

D. Change greet(42) to greet('42') to match string parameter.

Solution

1. Step 1: Check function parameter type

   The function expects a string parameter named name.

2. Step 2: Identify the call with wrong argument type

   The call greet(42) passes a number, which conflicts with the string type.

3. Step 3: Fix the call to match expected type

   Changing greet(42) to greet('42') passes a string, fixing the type mismatch.

4. Final Answer:

   Change greet(42) to greet('42') to match string parameter. -> Option D

5. Quick Check:

   Parameter type mismatch fixed by passing string [OK]

Hint: Match argument types to parameter types exactly [OK]

Common Mistakes:

• Ignoring type mismatch errors
• Removing return type instead of fixing input
• Changing parameter type without reason

5. You want a function that accepts either a string or number and returns a string describing the input type. Which typed function is correct?

hard

A. function describe(input: any): string {
return `Input: ${input}`;
}

B. function describe(input: string): string {
return `String: ${input}`;
}

C. function describe(input: string | number): string {
if (typeof input === 'string') return `String: ${input}`;
else return `Number: ${input}`;
}

D. function describe(input: number): string {
return `Number: ${input}`;
}

Solution

1. Step 1: Understand the input types needed

   The function must accept either string or number, so union type string | number is required.

2. Step 2: Check function logic and typing

   function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } uses union type and checks input type to return correct description. Options C and D accept only one type, A uses any which loses type safety.

3. Final Answer:

   function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } -> Option C

4. Quick Check:

   Union type with type check = function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } [OK]

Hint: Use union types and type checks for multiple input types [OK]

Common Mistakes:

• Using any type losing safety
• Accepting only one type instead of both
• Not checking input type before returning