Type conversion and casting in C Sharp (C#) - Time & Space Complexity

Time Complexity: Type conversion and casting

O(n)

Understanding Time Complexity

When we convert or cast types in C#, the computer does some work behind the scenes.

We want to know how this work grows when we do many conversions.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int[] numbers = new int[n];
for (int i = 0; i < n; i++)
{
    double converted = (double)numbers[i];
}
    

This code converts each integer in an array to a double one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Casting each integer to double inside a loop.
• How many times: Exactly once for each element, so n times.

How Execution Grows With Input

Each new item means one more conversion step, so work grows steadily with n.

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

Pattern observation: The work grows directly in proportion to the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to convert all items grows linearly as the list gets bigger.

Common Mistake

[X] Wrong: "Casting a single item takes longer as the list grows."

[OK] Correct: Each cast is a simple step and takes the same time no matter how many items there are.

Interview Connect

Understanding how simple operations like casting scale helps you explain code efficiency clearly and confidently.

Self-Check

"What if we cast inside a nested loop over the array twice? How would the time complexity change?"

Practice

1. What is the main difference between type conversion and casting in C#?

easy

A. Casting changes data to string only, conversion changes data to numbers only.

B. Casting is automatic, conversion always requires manual code.

C. Casting requires compatible types and uses parentheses, conversion can be safer and more flexible.

D. Casting works only with classes, conversion works only with structs.

Solution

1. Step 1: Understand casting in C#

   Casting uses parentheses and works only when types are compatible, like int to double or object to string.

2. Step 2: Understand conversion methods

   Conversion methods like Convert.ToInt32 or int.Parse are safer and can handle strings and other types more flexibly.

3. Final Answer:

   Casting requires compatible types and uses parentheses, conversion can be safer and more flexible. -> Option C

4. Quick Check:

   Casting vs Conversion = Casting requires compatible types and uses parentheses, conversion can be safer and more flexible. [OK]

Hint: Casting uses parentheses; conversion uses methods like Convert.ToInt32 [OK]

Common Mistakes:

• Thinking casting works with all types automatically
• Confusing conversion methods with casting syntax
• Assuming casting changes data format like conversion

2. Which of the following is the correct syntax to cast a double variable d to an int in C#?

easy

A. int i = (int)d;

B. int i = int(d);

C. int i = Convert.ToInt(d);

D. int i = d as int;

Solution

1. Step 1: Recall casting syntax in C#

   Casting uses parentheses with the target type before the variable, like (int)d.

2. Step 2: Check each option

   int i = (int)d; uses correct casting syntax. int i = int(d); is invalid syntax. int i = Convert.ToInt(d); uses wrong method name (should be Convert.ToInt32). int i = d as int; uses 'as' which works only with reference types.

3. Final Answer:

   int i = (int)d; -> Option A

4. Quick Check:

   Correct cast syntax = int i = (int)d; [OK]

Hint: Casting uses (type)variable syntax, not functions or 'as' keyword [OK]

Common Mistakes:

• Using 'as' keyword for value types
• Calling non-existent Convert.ToInt method
• Using function-like syntax for casting

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

double d = 9.7;
int i = (int)d;
Console.WriteLine(i);

medium

A. Compilation error

B. 10

C. 9.7

D. 9

Solution

1. Step 1: Understand casting from double to int

   Casting double to int truncates the decimal part, it does not round.

2. Step 2: Apply casting to value 9.7

   Truncating 9.7 results in 9, so i = 9.

3. Final Answer:

   9 -> Option D

4. Quick Check:

   Double to int cast truncates decimals = 9 [OK]

Hint: Casting double to int drops decimals, no rounding [OK]

Common Mistakes:

• Assuming casting rounds the number
• Expecting a compilation error
• Confusing output with original double value

4. Identify the error in this C# code snippet:

string s = "123abc";
int num = Convert.ToInt32(s);
Console.WriteLine(num);

medium

A. FormatException at runtime due to invalid string format

B. num will be 0 because of invalid characters

C. Compilation error because Convert.ToInt32 does not exist

D. No error, code runs and prints 123

Solution

1. Step 1: Understand Convert.ToInt32 behavior

   Convert.ToInt32 tries to convert the whole string to an integer and throws an exception if format is invalid.

2. Step 2: Analyze string "123abc"

   String contains non-digit characters, so conversion fails and throws FormatException at runtime.

3. Final Answer:

   FormatException at runtime due to invalid string format -> Option A

4. Quick Check:

   Invalid string format causes FormatException [OK]

Hint: Convert.ToInt32 throws error if string has non-digit chars [OK]

Common Mistakes:

• Assuming partial conversion succeeds
• Expecting zero instead of exception
• Thinking Convert.ToInt32 is compile-time error

5. You have an object obj that holds an integer value. Which code safely converts obj to an int without risking an exception if obj is not an int?

hard

A. int i = Convert.ToInt32(obj);

B. int i = obj is int val ? val : 0;

C. int i = obj as int;

D. int i = (int)obj;

Solution

1. Step 1: Understand casting and conversion risks

   Direct cast (int)obj throws exception if obj is not int. Convert.ToInt32 may throw exceptions too. 'as' cannot be used with value types like int.

2. Step 2: Analyze safe pattern

   Using pattern matching with 'is' checks type safely and assigns value or default 0 if not int, avoiding exceptions.

3. Final Answer:

   int i = obj is int val ? val : 0; -> Option B

4. Quick Check:

   Pattern matching safely converts or defaults = int i = obj is int val ? val : 0; [OK]

Hint: Use 'is' pattern matching to safely cast without exceptions [OK]

Common Mistakes:

• Using 'as' with value types causing compile errors
• Casting without checking type causing exceptions
• Assuming Convert.ToInt32 always safe