Nullable value types in C Sharp (C#) - Time & Space Complexity

Time Complexity: Nullable value types

O(n)

Understanding Time Complexity

Let's see how the time it takes to run code with nullable value types changes as the input grows.

We want to know how the program's steps increase when working with nullable values.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int?[] numbers = new int?[n];
for (int i = 0; i < n; i++)
{
    if (numbers[i].HasValue)
    {
        Console.WriteLine(numbers[i].Value);
    }
}
    

This code goes through an array of nullable integers and prints the value if it exists.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each element in the array once.
• How many times: Exactly n times, where n is the array size.

How Execution Grows With Input

As the array gets bigger, the program checks more elements one by one.

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

Pattern observation: The number of steps grows directly with the size of the input.

Final Time Complexity

Time Complexity: O(n)

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

Common Mistake

[X] Wrong: "Checking if a nullable has a value makes the code slower in a way that changes the overall time complexity."

[OK] Correct: Checking if a nullable has a value is a simple step done once per item, so it does not change the overall linear growth.

Interview Connect

Understanding how loops work with nullable types helps you explain how your code handles optional data efficiently.

Self-Check

"What if we nested another loop inside to check each element multiple times? How would the time complexity change?"

Practice

1. What does a nullable value type in C# allow you to do?

easy

A. Store only non-null values

B. Store values only in reference types

C. Store multiple values at once

D. Store a value or no value (null)

Solution

1. Step 1: Understand nullable value types

   Nullable value types allow a value type to hold either a normal value or no value (null).

2. Step 2: Compare options

   Only Store a value or no value (null) correctly describes this behavior; others are incorrect because value types normally cannot be null.

3. Final Answer:

   Store a value or no value (null) -> Option D

4. Quick Check:

   Nullable value type = value or null [OK]

Hint: Nullable means value or null, not multiple values [OK]

Common Mistakes:

• Thinking nullable stores multiple values
• Confusing nullable with reference types
• Assuming nullable cannot hold null

2. Which of the following is the correct syntax to declare a nullable integer in C#?

easy

A. int number?;

B. int? number;

C. nullable int number;

D. Nullable number int;

Solution

1. Step 1: Recall nullable syntax

   In C#, you add a question mark after the value type to make it nullable, like int?.

2. Step 2: Check each option

   Only int? number; uses the correct syntax int? number;. Others are invalid syntax.

3. Final Answer:

   int? number; -> Option B

4. Quick Check:

   Nullable int syntax = int? [OK]

Hint: Use ? right after type for nullable, like int? [OK]

Common Mistakes:

• Placing ? after variable name
• Using 'nullable' keyword incorrectly
• Mixing order of type and nullable

3. What is the output of this C# code?

int? x = null;
int y = x ?? 5;
Console.WriteLine(y);

medium

A. 0

B. null

C. 5

D. Compilation error

Solution

1. Step 1: Understand the null-coalescing operator

   The operator ?? returns the left value if not null; otherwise, it returns the right value.

2. Step 2: Apply to given code

   Since x is null, y gets the value 5, so Console.WriteLine(y); prints 5.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   x is null, so y = 5 [OK]

Hint: ?? returns right value if left is null [OK]

Common Mistakes:

• Assuming null prints as 0
• Confusing ?? with || operator
• Expecting compilation error for null assignment

4. Identify the error in this code snippet:

int? a = 10;
int b = a;
Console.WriteLine(b);

medium

A. Cannot assign nullable int to int without checking for null

B. Variable 'a' must be initialized

C. Console.WriteLine cannot print int values

D. No error, code runs fine

Solution

1. Step 1: Check assignment from nullable to non-nullable

   Assigning a nullable int directly to an int variable without checking for null causes a compile error.

2. Step 2: Explain why error occurs

   Because a might be null, C# requires explicit null check or use of .Value or null-coalescing operator.

3. Final Answer:

   Cannot assign nullable int to int without checking for null -> Option A

4. Quick Check:

   Nullable to int needs null check [OK]

Hint: Check nullable has value before assigning to non-nullable [OK]

Common Mistakes:

• Ignoring null check before assignment
• Assuming implicit conversion works
• Thinking Console.WriteLine causes error

5. Given a nullable double double? d = null;, which code safely assigns its value to a non-nullable double result with default 0.0 if d is null?

hard

A. double result = d ?? 0.0;

B. double result = d.Value;

C. double result = (double)d;

D. double result = d != null ? d : null;

Solution

1. Step 1: Understand safe assignment from nullable

   To assign a nullable to non-nullable safely, provide a default value if null using ??.

2. Step 2: Evaluate each option

   double result = d.Value; throws exception if d is null. double result = d ?? 0.0; uses ?? to assign 0.0 if null, which is safe. double result = (double)d; casts but throws if null. double result = d != null ? d : null; tries to assign null to non-nullable, invalid.

3. Final Answer:

   double result = d ?? 0.0; -> Option A

4. Quick Check:

   Use ?? to provide default for nullable [OK]

Hint: Use ?? operator to assign default if nullable is null [OK]

Common Mistakes:

• Using .Value without null check
• Casting nullable directly without check
• Assigning null to non-nullable variable