Non-distributive conditional types in Typescript - Time & Space Complexity

Time Complexity: Non-distributive conditional types

O(1)

Understanding Time Complexity

We want to understand how the time it takes to evaluate a non-distributive conditional type changes as the input type grows.

Specifically, how does TypeScript handle conditional checks when the input is a union type but the condition is made non-distributive?

Scenario Under Consideration

Analyze the time complexity of this TypeScript code snippet.

type NonDistributive = [T] extends [string | number] ? true : false;

// Example usage:
type Test1 = NonDistributive;
type Test2 = NonDistributive;

This code checks if a type T is assignable to string or number without distributing over unions.

Identify Repeating Operations

Look for repeated checks or evaluations inside the conditional type.

• Primary operation: TypeScript evaluates the conditional once on the whole type wrapped in a tuple to prevent distribution.
• How many times: Exactly once, regardless of how many union members T has.

How Execution Grows With Input

Since the conditional is non-distributive, the check happens once no matter how many types are in the union.

Input Size (n)	Approx. Operations
1 (e.g., string)	1
2 (e.g., string | number)	1
10 (e.g., union of 10 types)	1

Pattern observation: The number of operations stays the same even if the union grows larger.

Final Time Complexity

Time Complexity: O(1)

This means the evaluation time does not increase as the input type union grows.

Common Mistake

[X] Wrong: "The conditional type runs once for each member of the union, so time grows with union size."

[OK] Correct: Wrapping the type in a tuple disables distribution, so the check happens only once on the whole union.

Interview Connect

Understanding how TypeScript handles conditional types helps you write efficient type checks and reason about compiler performance in real projects.

Self-Check

What if we removed the tuple wrapping and let the conditional distribute over the union? How would the time complexity change?

Practice

1. What does a non-distributive conditional type in TypeScript do differently compared to a distributive conditional type?

easy

A. It converts all types to string before evaluation.

B. It always distributes the condition over each member of the union type.

C. It only works with primitive types, not unions.

D. It evaluates the condition on the entire union type as a whole, not on each member separately.

Solution

1. Step 1: Understand distributive conditional types

   Distributive conditional types apply the condition to each member of a union type separately.

2. Step 2: Understand non-distributive conditional types

   Non-distributive conditional types evaluate the condition on the entire union type as a single entity, not distributing over members.

3. Final Answer:

   It evaluates the condition on the entire union type as a whole, not on each member separately. -> Option D

4. Quick Check:

   Non-distributive = whole union check [OK]

Hint: Non-distributive means no splitting union, check whole type [OK]

Common Mistakes:

• Thinking conditional always distributes over unions
• Confusing non-distributive with type narrowing
• Assuming it only works on primitives

2. Which syntax correctly defines a non-distributive conditional type in TypeScript?

easy

A. type NonDist<T> = T | string ? true : false;

B. type NonDist<T> = T extends string ? true : false;

C. type NonDist<T> = [T] extends [string] ? true : false;

D. type NonDist<T> = T & string ? true : false;

Solution

1. Step 1: Recognize non-distributive syntax

   Wrapping the type parameter in a tuple, like [T], prevents distribution over unions.

2. Step 2: Compare options

   type NonDist<T> = [T] extends [string] ? true : false; uses [T] extends [string], which is the correct non-distributive syntax. type NonDist<T> = T extends string ? true : false; distributes over unions. Options C and D are invalid conditional syntax.

3. Final Answer:

   type NonDist<T> = [T] extends [string] ? true : false; -> Option C

4. Quick Check:

   Tuple wrapping disables distribution [OK]

Hint: Wrap type in tuple [T] to prevent distribution [OK]

Common Mistakes:

• Not wrapping type in tuple, causing distribution
• Using invalid conditional syntax
• Confusing union with intersection in condition

3. Given the code:

type Test<T> = T extends string ? 'yes' : 'no';
type Result = Test<'a' | number>;

What is the type of Result?

medium

A. 'yes' | 'no'

B. 'yes'

C. 'no'

D. Error

Solution

1. Step 1: Understand distributive conditional types

   Since T is a union 'a' | number, the condition distributes over each member.

2. Step 2: Evaluate each member

   'a' extends string is true, so 'yes'; number extends string is false, so 'no'. Combined result is 'yes' | 'no'.

3. Final Answer:

   'yes' | 'no' -> Option A

4. Quick Check:

   Distributes over union = 'yes' | 'no' [OK]

Hint: Conditional distributes over union unless wrapped [OK]

Common Mistakes:

• Assuming whole union checked at once
• Expecting only 'yes' or only 'no'
• Confusing union with intersection

4. Identify the error in this non-distributive conditional type:

type NonDist<T> = T extends [string] ? true : false;

medium

A. It incorrectly checks if T extends a tuple containing string, not preventing distribution.

B. It correctly prevents distribution by wrapping T in a tuple.

C. It causes a syntax error because of missing brackets.

D. It always returns false regardless of T.

Solution

1. Step 1: Analyze the condition

   The condition checks if T extends [string], a tuple type, not wrapping T.

2. Step 2: Understand distribution prevention

   To prevent distribution, T itself must be wrapped in a tuple: [T] extends [string]. This code does not do that, so distribution is not prevented.

3. Final Answer:

   It incorrectly checks if T extends a tuple containing string, not preventing distribution. -> Option A

4. Quick Check:

   Wrap T, not string, to prevent distribution [OK]

Hint: Wrap T in tuple, not the type to check [OK]

Common Mistakes:

• Wrapping the wrong side of extends
• Confusing tuple with type wrapper
• Assuming syntax error instead of logic error

5. How can you write a non-distributive conditional type that checks if a union type T is exactly string | number (no more, no less)?

hard

A. type Exact<T> = T extends string | number ? true : false;

B. type Exact<T> = [T] extends [string | number] ? ([string | number] extends [T] ? true : false) : false;

C. type Exact<T> = T extends [string | number] ? true : false;

D. type Exact<T> = [T] extends [string] | [number] ? true : false;

Solution

1. Step 1: Prevent distribution with tuple wrapping

   Wrapping T in a tuple [T] prevents distribution over unions.

2. Step 2: Use mutual assignability checks

   Check [T] extends [string | number] and [string | number] extends [T] to ensure exact match, no extra or missing types.

3. Final Answer:

   type Exact<T> = [T] extends [string | number] ? ([string | number] extends [T] ? true : false) : false; -> Option B

4. Quick Check:

   Tuple wrap + mutual extends = exact type check [OK]

Hint: Wrap T and check both extends directions for exact match [OK]

Common Mistakes:

• Not preventing distribution, causing partial matches
• Checking only one extends direction
• Using incorrect tuple wrapping