Namespace declaration in Typescript - Time & Space Complexity

Time Complexity: Namespace declaration

O(n)

Understanding Time Complexity

When we use namespaces in TypeScript, we group code together. It's important to see how this grouping affects how long the program takes to run.

We want to know: does using namespaces change how the program's speed grows as we add more code inside them?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

namespace MathUtils {
  export function square(n: number): number {
    return n * n;
  }

  export function sum(arr: number[]): number {
    let total = 0;
    for (const num of arr) {
      total += num;
    }
    return total;
  }
}
    

This code defines a namespace with two functions: one squares a number, the other sums an array of numbers.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for loop inside the sum function that goes through each number in the array.
• How many times: It runs once for every item in the input array.

How Execution Grows With Input

Explain the growth pattern intuitively.

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

Pattern observation: The time to sum numbers grows directly with how many numbers there are. More numbers mean more additions.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the sum function grows in a straight line with the size of the input array.

Common Mistake

[X] Wrong: "Using a namespace makes the code slower because it adds extra steps."

[OK] Correct: Namespaces only group code logically. They don't add loops or repeated work, so they don't change how long the code takes to run.

Interview Connect

Understanding how code grouping like namespaces affects performance helps you write clear and efficient programs. This skill shows you can think about both organization and speed.

Self-Check

"What if the sum function called another function inside the loop? How would that affect the time complexity?"

Practice

1. What is the main purpose of a namespace in TypeScript?

easy

A. To import external libraries

B. To create a new type of variable

C. To define a function that runs automatically

D. To group related code under one name and avoid name clashes

Solution

1. Step 1: Understand what namespaces do

   Namespaces group related code together to keep it organized.

2. Step 2: Recognize the benefit of namespaces

   They help avoid name clashes by keeping code under one name.

3. Final Answer:

   To group related code under one name and avoid name clashes -> Option D

4. Quick Check:

   Namespaces = Group code + avoid clashes [OK]

Hint: Namespaces group code to avoid name conflicts [OK]

Common Mistakes:

• Thinking namespaces create new variable types
• Confusing namespaces with functions
• Assuming namespaces import libraries

2. Which of the following is the correct syntax to declare a namespace named Utils in TypeScript?

easy

A. namespace Utils { }

B. module Utils { }

C. package Utils { }

D. namespace = Utils { }

Solution

1. Step 1: Recall the correct keyword for namespaces

   TypeScript uses the keyword namespace to declare namespaces.

2. Step 2: Check the syntax format

   The correct syntax is namespace Name { }, so namespace Utils { } is correct.

3. Final Answer:

   namespace Utils { } -> Option A

4. Quick Check:

   Namespace syntax = namespace Name { } [OK]

Hint: Use 'namespace Name { }' to declare namespaces [OK]

Common Mistakes:

• Using 'module' instead of 'namespace'
• Adding '=' sign in declaration
• Using 'package' keyword which is invalid

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

namespace MathOps {
  export function add(a: number, b: number) {
    return a + b;
  }
}

console.log(MathOps.add(3, 4));

medium

A. undefined

B. 7

C. Error: add is not defined

D. NaN

Solution

1. Step 1: Understand the namespace and export usage

   The function add is inside namespace MathOps and is exported, so it can be accessed outside.

2. Step 2: Evaluate the function call

   Calling MathOps.add(3, 4) returns 3 + 4 = 7.

3. Final Answer:

   7 -> Option B

4. Quick Check:

   Exported function call returns sum 7 [OK]

Hint: Exported namespace members are accessible outside [OK]

Common Mistakes:

• Forgetting to export the function
• Trying to call function without namespace prefix
• Expecting runtime errors due to namespace

4. Identify the error in this TypeScript namespace code:

namespace Data {
  function getData() {
    return "info";
  }
}

console.log(Data.getData());

medium

A. Function getData is not exported, so it cannot be accessed outside

B. Namespace name Data is invalid

C. Syntax error in namespace declaration

D. Console.log is misspelled

Solution

1. Step 1: Check function accessibility inside namespace

   The function getData is declared but not exported, so it's private to the namespace.

2. Step 2: Understand why console.log(Data.getData()) fails

   Since getData is not exported, it cannot be accessed outside the namespace, causing an error.

3. Final Answer:

   Function getData is not exported, so it cannot be accessed outside -> Option A

4. Quick Check:

   Export missing = access error [OK]

Hint: Export functions to access them outside namespaces [OK]

Common Mistakes:

• Assuming all namespace members are public by default
• Thinking namespace name is invalid
• Ignoring export keyword importance

5. Given two namespaces below, what is the correct way to call the log function from Logger inside App?

namespace Logger {
  export function log(message: string) {
    console.log("LOG: " + message);
  }
}

namespace App {
  export function run() {
    // Call Logger.log here
  }
}

App.run();

hard

A. log("App started");

B. App.Logger.log("App started");

C. Logger.log("App started");

D. Logger::log("App started");

Solution

1. Step 1: Understand namespace access rules

   Namespaces are accessed by their name followed by dot and member name, so Logger.log is correct.

2. Step 2: Check the options for calling the function

   Only Logger.log("App started") correctly calls the exported function from the Logger namespace.

3. Final Answer:

   Logger.log("App started"); -> Option C

4. Quick Check:

   Namespace function call = NamespaceName.member [OK]

Hint: Call namespace functions with NamespaceName.function() [OK]

Common Mistakes:

• Calling function without namespace prefix
• Using invalid syntax like '::'
• Assuming nested namespaces auto-import members