Type annotation on variables in Typescript - Time & Space Complexity

Time Complexity: Type annotation on variables

O(n)

Understanding Time Complexity

We look at how adding type annotations to variables affects the speed of a TypeScript program.

Does specifying types change how long the program takes to run?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

let total: number = 0;
const numbers: number[] = [1, 2, 3, 4, 5];

for (let i = 0; i < numbers.length; i++) {
  total += numbers[i];
}
console.log(total);
    

This code sums all numbers in an array using a variable with a type annotation.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that adds each number to total.
• How many times: Once for each item in the array.

How Execution Grows With Input

As the array gets bigger, the loop runs more times, adding each number once.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line with the input size.

Common Mistake

[X] Wrong: "Adding type annotations makes the program slower because it adds extra work."

[OK] Correct: Type annotations are used only during coding and checking, not when the program runs, so they do not slow down execution.

Interview Connect

Understanding that type annotations help with code clarity but do not affect runtime speed shows you know how TypeScript works behind the scenes.

Self-Check

"What if we replaced the for-loop with a built-in array method like .reduce()? How would the time complexity change?"

Practice

1. What does the type annotation let age: number; tell us about the variable age?

easy

A. It means age can hold any type of value.

B. It means age can only hold numbers.

C. It means age is a string variable.

D. It means age is a function.

Solution

1. Step 1: Understand type annotation syntax

   The colon : after age followed by number means age must hold a number value.

2. Step 2: Interpret the meaning of number

   The type number restricts the variable to only numeric values, no strings or other types allowed.

3. Final Answer:

   It means age can only hold numbers. -> Option B

4. Quick Check:

   Type annotation : number means only numbers [OK]

Hint: Colon after variable name means type follows [OK]

Common Mistakes:

• Thinking type annotation changes the value
• Confusing type annotation with assignment
• Assuming variable can hold any type without error

2. Which of the following is the correct way to add a type annotation for a string variable named name in TypeScript?

easy

A. let name string;

B. let name = string;

C. let name: string;

D. let name: "string";

Solution

1. Step 1: Recall correct syntax for type annotation

   Type annotation uses a colon : followed by the type name without quotes.

2. Step 2: Check each option

   let name: string; uses let name: string; which is correct syntax. Options B and C miss the colon or use wrong syntax. let name: "string"; uses quotes around string, which is incorrect.

3. Final Answer:

   let name: string; -> Option C

4. Quick Check:

   Use colon and type name without quotes [OK]

Hint: Use colon then type name without quotes [OK]

Common Mistakes:

• Omitting the colon between variable and type
• Putting type in quotes like a string value
• Using equals sign instead of colon for type

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

let count: number = 5;
count = 10;
console.log(count);

medium

A. 10

B. Error: Type mismatch

C. undefined

D. 5

Solution

1. Step 1: Analyze variable declaration and assignment

   count is declared as a number and initialized to 5, then reassigned to 10, which is valid.

2. Step 2: Understand console.log output

   The last assigned value is 10, so console.log(count) prints 10.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   Variable holds last assigned number value [OK]

Hint: Variable prints last assigned value [OK]

Common Mistakes:

• Thinking initial value 5 is printed
• Expecting error on reassignment with same type
• Confusing output with undefined

4. Identify the error in this TypeScript code:

let isActive: boolean = "true";

medium

A. No error, code is correct.

B. Missing semicolon at the end.

C. Variable name cannot be isActive.

D. Type mismatch: string assigned to boolean.

Solution

1. Step 1: Check type annotation and assigned value

   The variable isActive is typed as boolean but assigned a string value "true".

2. Step 2: Understand TypeScript type checking

   TypeScript does not allow assigning a string to a boolean variable, causing a type mismatch error.

3. Final Answer:

   Type mismatch: string assigned to boolean. -> Option D

4. Quick Check:

   Type annotation enforces matching value types [OK]

Hint: Check assigned value matches annotated type [OK]

Common Mistakes:

• Ignoring quotes around boolean values
• Assuming string "true" is same as boolean true
• Thinking semicolon or variable name causes error

5. You want to declare a variable data that can hold either a number or a string. Which is the correct TypeScript annotation?

hard

A. let data: number | string;

B. let data: number & string;

C. let data: number, string;

D. let data: (number string);

Solution

1. Step 1: Understand union types in TypeScript

   The pipe symbol | is used to allow a variable to hold one of multiple types.

2. Step 2: Evaluate each option

   let data: number | string; uses number | string which means data can be either number or string. let data: number & string; uses & which means intersection (both types at once), invalid here. Options C and D have incorrect syntax.

3. Final Answer:

   let data: number | string; -> Option A

4. Quick Check:

   Use | for multiple allowed types [OK]

Hint: Use pipe | to allow multiple types [OK]

Common Mistakes:

• Using & instead of | for multiple types
• Separating types with comma or space
• Putting types inside parentheses without operator