Properties vs fields in C Sharp (C#) - Performance Comparison

Time Complexity: Properties vs fields

O(n)

Understanding Time Complexity

We want to see how fast code runs when using properties compared to fields in C#.

How does accessing or setting values change as we do it more times?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Sample
{
    private int _field;
    public int Property { get; set; }

    public void UpdateValues(int n)
    {
        for (int i = 0; i < n; i++)
        {
            _field = i;
            Property = i;
        }
    }
}

This code sets a private field and a public property inside a loop that runs n times.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Assigning values to a field and a property inside a loop.
• How many times: The loop runs n times, so these assignments happen n times.

How Execution Grows With Input

Each time we increase n, the number of assignments grows the same amount.

Input Size (n)	Approx. Operations
10	20 assignments (10 to field + 10 to property)
100	200 assignments
1000	2000 assignments

Pattern observation: The total work grows directly with n, doubling because of two assignments per loop.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as the number of loop runs increases.

Common Mistake

[X] Wrong: "Accessing a property is always slower and changes the time complexity compared to a field."

[OK] Correct: Both field and property assignments happen once per loop iteration, so time grows linearly for both. The difference is tiny and does not change the overall growth pattern.

Interview Connect

Understanding how properties and fields behave in loops helps you explain performance clearly and shows you know how code runs as it scales.

Self-Check

"What if the property had extra logic inside its setter? How would that affect the time complexity?"

Practice

1. What is the main difference between a field and a property in C#?

easy

A. Properties store data directly, fields control access to data.

B. Fields and properties are exactly the same in C#.

C. Fields store data directly, properties control access to data.

D. Properties can only be used in structs, fields only in classes.

Solution

1. Step 1: Understand what a field does

   A field is a variable inside a class that holds data directly.

2. Step 2: Understand what a property does

   A property provides controlled access to data, often using get and set methods.

3. Final Answer:

   Fields store data directly, properties control access to data. -> Option C

4. Quick Check:

   Field = direct data, Property = controlled access [OK]

Hint: Fields hold data; properties manage access to it. [OK]

Common Mistakes:

• Confusing fields and properties as the same.
• Thinking properties store data directly.
• Believing fields control access like properties.

2. Which of the following is the correct syntax to declare a property named Age with a private field in C#?

easy

A. int Age; int Age { get; set; }

B. private int Age; public int Age { get; set; }

C. public int age; public int Age;

D. private int age; public int Age { get { return age; } set { age = value; } }

Solution

1. Step 1: Identify private field declaration

   The private field should be lowercase (e.g., age) and declared as private int age;.

2. Step 2: Identify property syntax

   The property Age uses get and set to access the private field correctly.

3. Final Answer:

   private int age; public int Age { get { return age; } set { age = value; } } -> Option D

4. Quick Check:

   Private field + property with get/set = correct syntax [OK]

Hint: Private field lowercase, property uppercase with get/set. [OK]

Common Mistakes:

• Using same name for field and property causing errors.
• Missing get or set in property.
• Declaring fields as public when they should be private.

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

class Person {
  private string name = "Alice";
  public string Name {
    get { return name; }
    set { name = value; }
  }
}

var p = new Person();
p.Name = "Bob";
Console.WriteLine(p.Name);

medium

A. Bob

B. name

C. Alice

D. Compilation error

Solution

1. Step 1: Understand property set operation

   The line p.Name = "Bob"; calls the set accessor, changing the private field name to "Bob".

2. Step 2: Understand property get operation

   The line Console.WriteLine(p.Name); calls the get accessor, returning the updated value "Bob".

3. Final Answer:

   Bob -> Option A

4. Quick Check:

   Property set changes value, get returns updated value [OK]

Hint: Property set changes field; get returns updated value. [OK]

Common Mistakes:

• Assuming output is original field value.
• Confusing field name with property name.
• Thinking code causes compilation error.

4. Identify the error in this code snippet:

class Car {
  public int speed;
  public int Speed {
    get { return speed; }
    set { speed = value; }
  }
}

var c = new Car();
c.Speed = 50;
Console.WriteLine(c.speed);

medium

A. Accessing field directly breaks encapsulation.

B. Field and property have the same name causing conflict.

C. No error; code works fine.

D. Property must be static to access field.

Solution

1. Step 1: Check field and property names

   The field is speed and property is Speed, so no naming conflict.

2. Step 2: Analyze direct field access

   Accessing c.speed directly bypasses the property, which can break encapsulation and safety.

3. Final Answer:

   Accessing field directly breaks encapsulation. -> Option A

4. Quick Check:

   Use properties to protect data, not direct field access [OK]

Hint: Avoid direct field access; use properties for safety. [OK]

Common Mistakes:

• Thinking same names cause error (case-sensitive).
• Believing direct field access is always safe.
• Assuming property must be static.

5. You want to create a class BankAccount where the Balance can be read publicly but only changed inside the class. Which is the best way to declare Balance?

hard

A. public decimal Balance; // public field

B. private decimal balance; public decimal Balance { get; private set; }

C. public decimal Balance { private get; set; }

D. private decimal Balance; public decimal balance { get; set; }

Solution

1. Step 1: Understand access needs

   Balance should be readable publicly but only settable privately inside the class.

2. Step 2: Choose property with private set

   Using public decimal Balance { get; private set; } allows public reading but restricts setting to inside the class.

3. Final Answer:

   private decimal balance; public decimal Balance { get; private set; } -> Option B

4. Quick Check:

   Public get + private set = controlled access [OK]

Hint: Use property with private set for controlled write access. [OK]

Common Mistakes:

• Using public field exposes data to unwanted changes.
• Setting private get hides data from outside.
• Confusing field and property naming conventions.