Type compatibility with classes in Typescript - Time & Space Complexity

Time Complexity: Type compatibility with classes

O(n)

Understanding Time Complexity

When working with classes in TypeScript, it's important to understand how type compatibility affects performance.

We want to see how the program's work grows when checking if one class type fits another.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Point {
  x: number;
  y: number;
  constructor(x: number, y: number) {
    this.x = x;
    this.y = y;
  }
}

function isCompatible(a: Point, b: Point): boolean {
  return a.x === b.x && a.y === b.y;
}

const p1 = new Point(1, 2);
const p2 = new Point(1, 2);
console.log(isCompatible(p1, p2));
    

This code checks if two Point objects have the same x and y values.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Comparing each property of the class instances.
• How many times: Once per property (here 2 properties: x and y).

How Execution Grows With Input

As the number of properties in the class grows, the number of comparisons grows too.

Input Size (number of properties)	Approx. Operations
2	2 comparisons
10	10 comparisons
100	100 comparisons

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

Final Time Complexity

Time Complexity: O(n)

This means the time to check compatibility grows in a straight line with the number of properties.

Common Mistake

[X] Wrong: "Type compatibility checks happen instantly no matter how many properties there are."

[OK] Correct: Each property must be checked, so more properties mean more work and longer checks.

Interview Connect

Understanding how type compatibility scales helps you write efficient code and explain your reasoning clearly in interviews.

Self-Check

"What if the class had nested objects as properties? How would the time complexity change?"

Practice

1. In TypeScript, when are two classes considered compatible for assignment?

easy

A. When they have the same number of methods

B. Only if they share the same class name

C. When their instances have matching properties and types

D. If they are declared in the same file

Solution

1. Step 1: Understand Type Compatibility

   TypeScript checks if the properties and their types in one class instance match those expected by another class type.

2. Step 2: Check Class Names and Methods

   Class names or method counts do not affect compatibility; only the shape (properties and types) matters.

3. Final Answer:

   When their instances have matching properties and types -> Option C

4. Quick Check:

   Compatibility = matching properties and types [OK]

Hint: Focus on properties and types, not class names [OK]

Common Mistakes:

• Assuming class names must match
• Thinking method count matters
• Believing file location affects compatibility

2. Which of the following is the correct syntax to assign an instance of class B to a variable typed as class A in TypeScript, assuming compatibility?

easy

A. let a: B = A();

B. let a: A = new B();

C. let a = A(new B());

D. let a = new A(B);

Solution

1. Step 1: Review TypeScript Assignment Syntax

   To assign an instance of class B to a variable typed as A, use let a: A = new B(); if B is compatible with A.

2. Step 2: Identify Incorrect Syntax

   Other options misuse constructor calls or type annotations and are invalid.

3. Final Answer:

   let a: A = new B(); -> Option B

4. Quick Check:

   Use let var: Type = new Class(); [OK]

Hint: Use variable: Type = new Class() for assignments [OK]

Common Mistakes:

• Calling classes like functions
• Swapping variable and type names
• Using incorrect constructor syntax

3. Consider the following TypeScript code:

class A { x: number; }
class B { x: number; y: string; }

let a: A = new B();
console.log(a.x);

What will be the output when this code runs?

medium

A. undefined

B. Runtime error

C. The value of x from B instance

D. Compilation error

Solution

1. Step 1: Analyze Class Properties and Assignment

   Class B has properties x and y. Class A has only x. Assigning new B() to a variable typed as A is allowed because B has at least the properties of A.

2. Step 2: Check Output of console.log(a.x)

   The property x exists on the B instance. Since no value is assigned to x, it is undefined, so console.log(a.x) outputs "undefined".

3. Final Answer:

   undefined -> Option A

4. Quick Check:

   Compatible class instance property accessed correctly [OK]

Hint: Compatible class instances share accessible properties [OK]

Common Mistakes:

• Expecting runtime error due to extra properties
• Thinking assignment causes compilation error
• Assuming class properties are auto-initialized to 0

4. Given the code below, why does TypeScript show an error?

class A { x: number; }
class B { y: string; }

let a: A = new B();

medium

A. Because new B() is not a valid constructor call

B. Because class names differ

C. Because B has extra property y

D. Because B does not have property x required by A

Solution

1. Step 1: Check Property Compatibility

   Class A requires property x. Class B only has property y, so B instances lack x.

2. Step 2: Understand TypeScript Compatibility Rules

   TypeScript requires the assigned instance to have all properties of the target type. Missing x causes error.

3. Final Answer:

   Because B does not have property x required by A -> Option D

4. Quick Check:

   Missing required property causes error [OK]

Hint: Check if assigned class has all required properties [OK]

Common Mistakes:

• Thinking class names must match
• Assuming extra properties cause error
• Believing constructor call is invalid

5. You have two classes:

class Person { name: string; age: number; }
class Employee { name: string; age: number; salary: number; }

Which assignment is valid and why?
let p: Person = new Employee();
let e: Employee = new Person();

hard

A. Only let p: Person = new Employee(); is valid because Employee has all Person properties

B. Only let e: Employee = new Person(); is valid because Person has fewer properties

C. Both assignments are valid because classes share some properties

D. Neither assignment is valid due to different class names

Solution

1. Step 1: Compare Properties of Person and Employee

   Employee has all properties of Person plus salary. Person lacks salary.

2. Step 2: Check Assignment Compatibility

   Assigning Employee instance to Person variable is valid (extra properties allowed). Assigning Person instance to Employee variable is invalid (missing salary).

3. Final Answer:

   Only let p: Person = new Employee(); is valid because Employee has all Person properties -> Option A

4. Quick Check:

   Extra properties allowed, missing properties not [OK]

Hint: Assign subclass to superclass type, not vice versa [OK]

Common Mistakes:

• Assuming both assignments are valid
• Confusing extra vs missing properties
• Thinking class names affect compatibility