Const enums and optimization in Typescript - Time & Space Complexity

Time Complexity: Const enums and optimization

O(n)

Understanding Time Complexity

We want to see how using const enums affects the speed of our TypeScript code.

How does the program's work change when const enums are used?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

const enum Colors {
  Red,
  Green,
  Blue
}

function getColorName(color: Colors): string {
  switch(color) {
    case Colors.Red: return "Red";
    case Colors.Green: return "Green";
    case Colors.Blue: return "Blue";
  }
  // Added default case to avoid missing return
  return "Unknown";
}

const colorName = getColorName(Colors.Green);

This code uses a const enum to represent colors and a function to get the color name.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The switch statement runs once per function call.
• How many times: Once for each call to getColorName.

How Execution Grows With Input

Since the enum values are replaced at compile time, the function runs with simple values.

Input Size (n)	Approx. Operations
10	10 simple switch checks
100	100 simple switch checks
1000	1000 simple switch checks

Pattern observation: The work grows linearly with the number of calls, but each call is very fast due to compile-time replacement.

Final Time Complexity

Time Complexity: O(n)

This means the time grows directly with how many times the function is called, but each call is very efficient.

Common Mistake

[X] Wrong: "Using const enums makes the code run in constant time no matter how many calls there are."

[OK] Correct: Each function call still runs the switch, so time grows with calls, but const enums make each call faster by replacing values early.

Interview Connect

Understanding how compile-time features like const enums affect runtime helps you write faster code and explain your choices clearly.

Self-Check

"What if we replaced the const enum with a regular enum? How would the time complexity and runtime behavior change?"

Practice

1. What is the main benefit of using const enum in TypeScript?

easy

A. It allows enums to be modified at runtime.

B. It enables enums to be serialized to JSON automatically.

C. It replaces enum references with actual values at compile time, reducing runtime code.

D. It creates a separate JavaScript object for the enum at runtime.

Solution

1. Step 1: Understand what const enum does

   const enum replaces enum references with their actual values during compilation, so no enum object exists at runtime.

2. Step 2: Compare runtime behavior

   Unlike regular enums, const enum does not generate extra JavaScript code for the enum object, reducing code size and improving speed.

3. Final Answer:

   It replaces enum references with actual values at compile time, reducing runtime code. -> Option C

4. Quick Check:

   Const enums optimize code by replacing references with values [OK]

Hint: Const enums inline values, no runtime object created [OK]

Common Mistakes:

• Thinking const enums create runtime objects
• Believing const enums allow runtime modification
• Confusing const enums with regular enums

2. Which of the following is the correct syntax to declare a const enum in TypeScript?

easy

A. enum Colors { Red, Green, Blue }

B. const enum Colors { Red, Green, Blue }

C. constant enum Colors { Red, Green, Blue }

D. enum const Colors { Red, Green, Blue }

Solution

1. Step 1: Recall the correct keyword order

   The correct syntax uses the keyword const before enum to declare a const enum.

2. Step 2: Check each option

   const enum Colors { Red, Green, Blue } matches the correct syntax: const enum Colors { Red, Green, Blue }. Options C and D use invalid keywords or order.

3. Final Answer:

   const enum Colors { Red, Green, Blue } -> Option B

4. Quick Check:

   Const enum syntax = const enum [OK]

Hint: Remember: const comes before enum in declaration [OK]

Common Mistakes:

• Writing 'constant' instead of 'const'
• Placing 'const' after 'enum'
• Omitting 'const' keyword

3. Given the following code, what will be the output when compiled and run?

const enum Direction {
  Up = 1,
  Down,
  Left,
  Right
}

const move = Direction.Left;
console.log(move);

medium

A. 3

B. undefined

C. Left

D. 2

Solution

1. Step 1: Understand enum value assignment

   The enum starts with Up = 1, so Down = 2, Left = 3, and Right = 4.

2. Step 2: Identify the value of Direction.Left

   It is 3, so move is assigned 3, and console.log(move) prints 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Enum Left value = 3 [OK]

Hint: Count enum values starting from assigned number [OK]

Common Mistakes:

• Assuming Left is 2 instead of 3
• Expecting string output 'Left'
• Confusing enum with object property

4. What is the error in the following TypeScript code using const enums?

const enum Status {
  Active = 1,
  Inactive = 0
}

console.log(Status[1]);

medium

A. Compile-time error: Cannot use reverse mapping with const enums

B. Runtime error: Status is undefined

C. No error, outputs 'Active'

D. Outputs 1

Solution

1. Step 1: Understand const enum limitations

   Const enums do not generate an object at runtime, so reverse mapping (accessing by index) is not supported.

2. Step 2: Identify the error cause

   Using Status[1] tries to access reverse mapping, causing a compile-time error.

3. Final Answer:

   Compile-time error: Cannot use reverse mapping with const enums -> Option A

4. Quick Check:

   Reverse mapping disallowed in const enums [OK]

Hint: Const enums have no reverse mapping, avoid index access [OK]

Common Mistakes:

• Expecting reverse mapping to work with const enums
• Thinking it outputs string 'Active'
• Ignoring compile-time errors

5. You want to optimize a TypeScript program by replacing a regular enum with a const enum. Which of the following changes will NOT work correctly after this replacement?

hard

A. Using enum values directly in expressions and comparisons.

B. Using enum values as keys in a switch statement.

C. Assigning enum values to variables for later use.

D. Accessing enum values by their numeric index (reverse mapping).

Solution

1. Step 1: Recall const enum behavior

   Const enums inline values and do not create runtime objects, so reverse mapping (index to name) is not available.

2. Step 2: Analyze each option

   Options A, B, and D work fine as they use the inlined values directly. Accessing enum values by their numeric index (reverse mapping). requires reverse mapping, which fails with const enums.

3. Final Answer:

   Accessing enum values by their numeric index (reverse mapping). -> Option D

4. Quick Check:

   Reverse mapping breaks with const enums [OK]

Hint: Const enums disallow reverse mapping, avoid numeric index access [OK]

Common Mistakes:

• Assuming all enum features work with const enums
• Using reverse mapping without error
• Confusing const enum with regular enum behavior