Common string methods in C Sharp (C#) - Time & Space Complexity

Time Complexity: Common string methods

O(n)

Understanding Time Complexity

When we use common string methods, it is important to know how the time to run them changes as the string gets longer.

We want to understand how the work done grows when the input string size grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

string input = "hello world";
string upper = input.ToUpper();
int index = input.IndexOf('o');
string sub = input.Substring(0, 5);
bool contains = input.Contains("wor");

This code uses common string methods to change case, find a character, get a part of the string, and check if a substring exists.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Each method scans or processes characters in the string.
• How many times: Usually once over the string or part of it.

How Execution Grows With Input

As the string gets longer, these methods take more time roughly proportional to the string length.

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

Pattern observation: The work grows in a straight line with the string size.

Final Time Complexity

Time Complexity: O(n)

This means the time to run these string methods grows directly with the length of the string.

Common Mistake

[X] Wrong: "String methods always run instantly no matter the string size."

[OK] Correct: Actually, many string methods look at each character, so longer strings take more time.

Interview Connect

Knowing how string methods scale helps you write efficient code and explain your choices clearly in interviews.

Self-Check

"What if we used a method that compares two strings character by character? How would the time complexity change if the strings are very long?"

Practice

1. Which C# string method returns a new string with all characters converted to uppercase?

easy

A. Substring()

B. Trim()

C. Contains()

D. ToUpper()

Solution

1. Step 1: Understand the purpose of ToUpper()

   The ToUpper() method converts all letters in a string to uppercase and returns a new string.

2. Step 2: Compare with other methods

   Trim() removes spaces, Contains() checks for substring presence, Substring() extracts part of the string.

3. Final Answer:

   ToUpper() -> Option D

4. Quick Check:

   Uppercase conversion = ToUpper() [OK]

Hint: Uppercase all letters? Use ToUpper() method [OK]

Common Mistakes:

• Confusing ToUpper() with ToLower()
• Using Trim() to change case
• Thinking Contains() changes text

2. Which of the following is the correct syntax to check if the string text contains the word "hello"?

easy

A. Contains(text, "hello")

B. text.Contains = "hello"

C. text.Contains("hello")

D. text.Has("hello")

Solution

1. Step 1: Recall the correct method call syntax

   In C#, to check if a string contains another, use the instance method with parentheses: text.Contains("hello").

2. Step 2: Identify incorrect syntax

   Assignments (=) or wrong method names like Has() are invalid for this check.

3. Final Answer:

   text.Contains("hello") -> Option C

4. Quick Check:

   Method call with parentheses = Contains() [OK]

Hint: Use text.Contains("word") with parentheses [OK]

Common Mistakes:

• Using assignment instead of method call
• Wrong method name like Has()
• Passing parameters incorrectly

3. What is the output of the following code?

string s = "  Hello World  ";
string result = s.Trim().Substring(0, 5);
Console.WriteLine(result);

medium

A. " Hel"

B. "Hello"

C. "Hello "

D. "Hello World"

Solution

1. Step 1: Apply Trim() method

   Trim() removes spaces at the start and end, so " Hello World " becomes "Hello World".

2. Step 2: Apply Substring(0, 5)

   Substring(0, 5) extracts characters from index 0 to 4, which is "Hello".

3. Final Answer:

   "Hello" -> Option B

4. Quick Check:

   Trim + Substring(0,5) = "Hello" [OK]

Hint: Trim removes spaces; Substring extracts exact part [OK]

Common Mistakes:

• Not trimming before substring
• Counting spaces in substring
• Confusing substring length

4. Identify the error in this code snippet:

string s = "Example";
if(s.Contains("ex"))
{
    Console.WriteLine("Found");
}

medium

A. Contains() is case-sensitive, so "ex" won't match "Ex"

B. Missing semicolon after if statement

C. Contains() method does not exist for strings

D. Console.WriteLine syntax is incorrect

Solution

1. Step 1: Check Contains() behavior

   Contains() is case-sensitive, so "ex" does not match "Ex" in "Example".

2. Step 2: Verify syntax correctness

   Semicolons and method calls are correct; no syntax errors present.

3. Final Answer:

   Contains() is case-sensitive, so "ex" won't match "Ex" -> Option A

4. Quick Check:

   Contains() case matters = true [OK]

Hint: Remember Contains() is case-sensitive by default [OK]

Common Mistakes:

• Assuming Contains() ignores case
• Looking for syntax errors that don't exist
• Confusing method availability

5. You want to extract the domain name from an email string email = "[e-mail]". Which code correctly extracts "example" using common string methods?

hard

A. string domain = email.Substring(email.IndexOf('@') + 1).Split('.')[0];

B. string domain = email.Trim().ToUpper();

C. string domain = email.Contains("@example");

D. string domain = email.Substring(0, email.IndexOf('.'));

Solution

1. Step 1: Find position after '@'

   email.IndexOf('@') finds the '@' position; adding 1 moves to start of domain.

2. Step 2: Extract substring from domain start and split by '.'

   Substring gets "example.com", then Split('.')[0] gets "example".

3. Step 3: Check other options

   B changes case, C returns bool, D extracts wrong part before '@'.

4. Final Answer:

   string domain = email.Substring(email.IndexOf('@') + 1).Split('.')[0]; -> Option A

5. Quick Check:

   Extract domain by substring + split = string domain = email.Substring(email.IndexOf('@') + 1).Split('.')[0]; [OK]

Hint: Use IndexOf('@') + Substring + Split('.') to get domain [OK]

Common Mistakes:

• Using Contains() instead of extracting
• Trimming or changing case wrongly
• Extracting before '@' instead of after