Throwing errors in Javascript - Time & Space Complexity

Time Complexity: Throwing errors

O(n)

Understanding Time Complexity

When we throw errors in JavaScript, it's important to know how this affects the program's speed as it runs.

We want to see how the time to run changes when errors happen inside loops or repeated code.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function checkNumbers(arr) {
  for (let i = 0; i < arr.length; i++) {
    if (arr[i] < 0) {
      throw new Error('Negative number found');
    }
  }
  return true;
}

This code checks each number in an array and throws an error if it finds a negative number.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each element of the array.
• How many times: Up to the length of the array, once per element.

How Execution Grows With Input

As the array gets bigger, the loop runs more times, checking each number until it finds a negative or finishes.

Input Size (n)	Approx. Operations
10	Up to 10 checks
100	Up to 100 checks
1000	Up to 1000 checks

Pattern observation: The number of checks grows directly with the size of the array.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of items checked.

Common Mistake

[X] Wrong: "Throwing an error inside a loop makes the whole loop run slower every time."

[OK] Correct: The loop stops as soon as the error is thrown, so it doesn't always run through all items. The error itself doesn't slow down each check.

Interview Connect

Understanding how throwing errors affects loops helps you explain how your code handles problems efficiently and when it stops work early.

Self-Check

"What if we changed the code to collect all negative numbers before throwing a single error? How would the time complexity change?"

Practice

1. What does the throw statement do in JavaScript?

easy

A. Stops the program and creates an error.

B. Catches an error and handles it.

C. Declares a new variable.

D. Runs a function asynchronously.

Solution

1. Step 1: Understand the purpose of throw

   The throw statement is used to create an error and stop normal program execution.

2. Step 2: Differentiate from error handling

   Unlike try...catch which handles errors, throw actually creates the error.

3. Final Answer:

   Stops the program and creates an error. -> Option A

4. Quick Check:

   throw creates error = A [OK]

Hint: Remember: throw creates errors, try...catch handles them [OK]

Common Mistakes:

• Confusing throw with try...catch
• Thinking throw handles errors
• Believing throw declares variables

2. Which of the following is the correct syntax to throw a new error with the message "Invalid input"?

easy

A. throw 'Invalid input';

B. throw error('Invalid input');

C. throw new Error('Invalid input');

D. throw new error('Invalid input');

Solution

1. Step 1: Recall the correct Error constructor usage

   In JavaScript, to create an error object, use new Error('message').

2. Step 2: Check syntax correctness

   Only throw new Error('Invalid input'); uses throw new Error('Invalid input'); which is correct syntax.

3. Final Answer:

   throw new Error('Invalid input'); -> Option C

4. Quick Check:

   Correct syntax uses new Error = C [OK]

Hint: Always use 'throw new Error' with capital E [OK]

Common Mistakes:

• Missing 'new' keyword
• Using lowercase 'error' instead of 'Error'
• Omitting parentheses

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

try {
  throw new Error('Oops!');
} catch (e) {
  console.log(e.message);
}

medium

A. Oops!

B. Error: Oops!

C. undefined

D. No output

Solution

1. Step 1: Understand the throw and catch behavior

   The code throws an error with message 'Oops!'. The catch block catches it and logs e.message.

2. Step 2: Determine what e.message contains

   e.message is the string 'Oops!'. So console.log(e.message) prints 'Oops!'.

3. Final Answer:

   Oops! -> Option A

4. Quick Check:

   Logging error message prints 'Oops!' = A [OK]

Hint: Catch error and log e.message to see the message [OK]

Common Mistakes:

• Printing whole error object instead of message
• Expecting 'Error: Oops!' instead of just message
• Thinking no output occurs

4. Identify the error in this code snippet:

try {
  throw new Error('Fail');
} catch e {
  console.log(e.message);
}

medium

A. Incorrect use of throw keyword.

B. No error; code runs fine.

C. Error message string is invalid.

D. Missing parentheses around catch parameter.

Solution

1. Step 1: Check catch syntax

   In JavaScript, the catch block must have parentheses around the error parameter, like catch (e).

2. Step 2: Identify the syntax error

   The code uses catch e without parentheses, which causes a syntax error.

3. Final Answer:

   Missing parentheses around catch parameter. -> Option D

4. Quick Check:

   Catch parameter needs parentheses = B [OK]

Hint: Always write catch with parentheses: catch (e) [OK]

Common Mistakes:

• Omitting parentheses in catch
• Misplacing throw statement
• Confusing error message with syntax error

5. You want to throw an error only if a user input is empty or null. Which code correctly throws an error in this case?

hard

A. if (input) throw new Error('Input required');

B. if (!input) throw new Error('Input required');

C. if (input == null) throw new error('Input required');

D. if (input === '') throw Error('Input required');

Solution

1. Step 1: Understand falsy values for empty or null input

   In JavaScript, !input is true if input is null, undefined, empty string, 0, or false.

2. Step 2: Check which option correctly throws error for empty or null

   if (!input) throw new Error('Input required'); uses if (!input) throw new Error('Input required'); which covers empty string and null correctly with proper syntax.

3. Final Answer:

   if (!input) throw new Error('Input required'); -> Option B

4. Quick Check:

   Use !input to check empty/null and throw Error = D [OK]

Hint: Use if (!input) to catch empty or null inputs [OK]

Common Mistakes:

• Using lowercase 'error' instead of 'Error'
• Throwing error only for empty string but missing null
• Throwing error when input is valid