How assignment compatibility is checked in Typescript - Performance & Efficiency

Time Complexity: How assignment compatibility is checked

O(n)

Understanding Time Complexity

We want to understand how TypeScript checks if one value can be assigned to another.

How much work does TypeScript do as types get bigger or more complex?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

interface Point {
  x: number;
  y: number;
}

const p1: Point = { x: 1, y: 2 };
const p2 = { x: 3, y: 4, z: 5 };

const p3: Point = p2; // assignment compatibility check
    

This code checks if the object p2 can be assigned to the type Point.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each property in the target type against the source type.
• How many times: Once for each property in the target type (here, 2 properties: x and y).

How Execution Grows With Input

As the number of properties in the target type grows, TypeScript checks each one.

Input Size (n properties)	Approx. Operations
10	About 10 property checks
100	About 100 property checks
1000	About 1000 property checks

Pattern observation: The work grows directly with the number of properties to check.

Final Time Complexity

Time Complexity: O(n)

This means the checking time grows in a straight line as the number of properties increases.

Common Mistake

[X] Wrong: "Assignment compatibility is instant no matter how big the types are."

[OK] Correct: TypeScript must check each property to be sure, so bigger types take more time.

Interview Connect

Understanding how TypeScript checks assignment helps you reason about type safety and performance in real projects.

Self-Check

"What if the source type has nested objects? How would that affect the time complexity?"

Practice

1. In TypeScript, what does assignment compatibility primarily check between two types?

easy

A. If the types have the same number of methods

B. If the variable names are the same

C. If the values are equal at runtime

D. If the properties and their types match between the source and target types

Solution

1. Step 1: Understand assignment compatibility concept

   TypeScript checks if the shape (properties and their types) of one type fits into another.

2. Step 2: Compare properties and types

   It does not check variable names or runtime values but the structure of types.

3. Final Answer:

   If the properties and their types match between the source and target types -> Option D

4. Quick Check:

   Shape matching = Properties and types [OK]

Hint: Think of matching shapes, not names or values [OK]

Common Mistakes:

• Confusing variable names with type compatibility
• Thinking runtime values affect assignment compatibility
• Assuming method count matters instead of properties

2. Which of the following is the correct syntax to assign an object of type {name: string} to a variable of type {name: string; age?: number} in TypeScript?

easy

A. let person: {name: string; age: number} = {age: 30};

B. let person: {name: string; age?: number} = {name: 'Alice'};

C. let person: {name: string; age: number} = {name: 'Alice'};

D. let person: {name: string} = {name: 'Alice', age: 30};

Solution

1. Step 1: Check optional property usage

   The target type has an optional property age?, so the source object can omit it.

2. Step 2: Verify assignment compatibility

   Assigning {name: 'Alice'} to {name: string; age?: number} is valid because age is optional.

3. Final Answer:

   let person: {name: string; age?: number} = {name: 'Alice'}; -> Option B

4. Quick Check:

   Optional properties can be omitted [OK]

Hint: Optional properties can be left out in assignments [OK]

Common Mistakes:

• Assigning object missing required properties
• Confusing optional and required properties
• Assigning extra properties to narrower types

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

interface A { x: number; }
interface B { x: number; y: number; }

let a: A = { x: 10 };
let b: B = { x: 10, y: 20 };

// Assignment
let c: A = b;
console.log(c.x);

medium

A. 10

B. 20

C. undefined

D. Compilation error

Solution

1. Step 1: Understand assignment compatibility from B to A

   Type B has all properties of A plus extra. Assigning B to A is allowed because A's shape is a subset of B's.

2. Step 2: Check the value of c.x

   Since b.x is 10, c.x will be 10 after assignment.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   Subset shape assignment = Allowed and value preserved [OK]

Hint: Assign wider type to narrower type if subset matches [OK]

Common Mistakes:

• Expecting error when assigning wider to narrower type
• Confusing property values with property names
• Thinking extra properties cause errors

4. Identify the error in this TypeScript code snippet:

interface Person { name: string; age: number; }

let p: Person = { name: 'Bob' };

medium

A. Missing property 'age' in the object assigned to 'p'

B. Property 'name' should be a number, not a string

C. Interface 'Person' cannot be used as a type

D. No error, code is valid

Solution

1. Step 1: Check required properties in interface

   The interface requires both name and age properties.

2. Step 2: Verify object assigned to variable

   The object only has name, missing age, causing a type error.

3. Final Answer:

   Missing property 'age' in the object assigned to 'p' -> Option A

4. Quick Check:

   All required properties must be present [OK]

Hint: Check all required properties are present in assigned object [OK]

Common Mistakes:

• Ignoring missing required properties
• Assuming optional properties are required
• Thinking interface cannot be used as type

5. Given these interfaces:

interface X { a: number; b: string; }
interface Y { a: number; b: string; c?: boolean; }

Which assignment is valid and why?

let x: X = { a: 1, b: 'hello' };
let y: Y = { a: 1, b: 'hello', c: true };

// Assignments
x = y;
y = x;

hard

A. Both assignments are valid because optional properties don't matter

B. Only y = x is valid because X has fewer properties

C. Only x = y is valid because Y has all properties of X plus optional ones

D. Both assignments are invalid due to property mismatch

Solution

1. Step 1: Analyze x = y assignment

   Y has all properties of X plus an optional c. Assigning Y to X is allowed because X's shape is a subset of Y's.

2. Step 2: Analyze y = x assignment

   X lacks property c which Y expects optionally. Assigning X to Y is not allowed because c might be missing and is optional but not guaranteed.

3. Step 3: Reconsider optional property assignment rules

   Assigning X to Y is invalid because Y expects c optionally, but the source object does not have it, and TypeScript does not allow missing optional properties when assigning to a type that includes them.

4. Final Answer:

   Only x = y is valid because Y has all properties of X plus optional ones -> Option C

5. Quick Check:

   Optional properties allow assignment from wider to narrower types only [OK]

Hint: Optional properties allow assignment from wider to narrower types only [OK]

Common Mistakes:

• Thinking optional properties block assignment both ways
• Assuming extra properties cause errors always
• Confusing required and optional properties