When to use abstract vs concrete in C Sharp (C#) - Performance Comparison

Time Complexity: When to use abstract vs concrete

O(n)

Understanding Time Complexity

We want to understand how choosing abstract or concrete classes affects the time your program takes to run.

Specifically, how does this choice impact the number of steps your program performs as it grows?

Scenario Under Consideration

Analyze the time complexity of this example using abstract and concrete classes.

abstract class Animal
{
    public abstract void Speak();
}

class Dog : Animal
{
    public override void Speak() => Console.WriteLine("Woof");
}

class Program
{
    static void MakeAnimalsSpeak(List animals)
    {
        foreach (var animal in animals)
            animal.Speak();
    }
}
    

This code uses an abstract class Animal with a Speak method, and a concrete class Dog that implements it. The program calls Speak on a list of animals.

Identify Repeating Operations

Look at what repeats when the program runs.

• Primary operation: Calling the Speak method on each animal in the list.
• How many times: Once for each animal in the list (loop runs n times).

How Execution Grows With Input

As the number of animals grows, the program calls Speak more times.

Input Size (n)	Approx. Operations
10	10 calls to Speak
100	100 calls to Speak
1000	1000 calls to Speak

Pattern observation: The number of operations grows directly with the number of animals.

Final Time Complexity

Time Complexity: O(n)

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

Common Mistake

[X] Wrong: "Using abstract classes makes the program slower because of extra method calls."

[OK] Correct: The extra method call cost is very small and does not change how the total time grows with input size.

Interview Connect

Understanding when to use abstract versus concrete classes shows you can design clear, flexible code without hurting performance as your program grows.

Self-Check

What if we replaced the abstract class with interfaces? How would the time complexity change?

Practice

1. Which statement best describes when to use an abstract class in C#?

easy

A. When you want to define a common plan without providing full implementation.

B. When you want to create a fully working class that can be instantiated.

C. When you want to prevent inheritance altogether.

D. When you want to create a class with only static methods.

Solution

1. Step 1: Understand abstract class purpose

   An abstract class defines methods or properties that must be implemented by subclasses but does not provide full implementation itself.

2. Step 2: Compare with concrete class

   Concrete classes provide full working code and can be instantiated, unlike abstract classes.

3. Final Answer:

   When you want to define a common plan without providing full implementation. -> Option A

4. Quick Check:

   Abstract class = common plan without full code [OK]

Hint: Abstract = plan only, Concrete = full working code [OK]

Common Mistakes:

• Confusing abstract with concrete classes
• Thinking abstract classes can be instantiated
• Believing abstract classes provide full method bodies

2. Which of the following is the correct way to declare an abstract class in C#?

easy

A. class abstract Vehicle { }

B. public abstract class Vehicle { }

C. abstract public Vehicle { }

D. public class abstract Vehicle { }

Solution

1. Step 1: Recall C# syntax for abstract classes

   The correct syntax places the keyword abstract before class and then the class name.

2. Step 2: Check each option

   public abstract class Vehicle { } uses public abstract class Vehicle { }, which is correct. Other options have incorrect keyword order or missing keywords.

3. Final Answer:

   public abstract class Vehicle { } -> Option B

4. Quick Check:

   abstract class syntax = 'public abstract class' [OK]

Hint: Use 'abstract' before 'class' keyword [OK]

Common Mistakes:

• Placing 'abstract' after 'class'
• Omitting 'class' keyword
• Incorrect keyword order

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

abstract class Animal {
    public abstract void Speak();
}

class Dog : Animal {
    public override void Speak() {
        Console.WriteLine("Woof");
    }
}

class Program {
    static void Main() {
        Animal a = new Dog();
        a.Speak();
    }
}

medium

A. Runtime error because Speak is abstract

B. Compile-time error because Animal is abstract

C. Woof

D. No output

Solution

1. Step 1: Understand abstract method implementation

   The abstract method Speak in Animal is overridden in Dog with a concrete implementation that prints "Woof".

2. Step 2: Analyze runtime behavior

   Creating an Animal reference to a Dog object and calling Speak() calls the overridden method, printing "Woof".

3. Final Answer:

   Woof -> Option C

4. Quick Check:

   Abstract method overridden = prints 'Woof' [OK]

Hint: Abstract method must be overridden to run [OK]

Common Mistakes:

• Thinking abstract class cannot be referenced
• Expecting compile or runtime error
• Assuming abstract methods have bodies

4. Identify the error in this code snippet:

abstract class Shape {
    public abstract double Area();
}

class Circle : Shape {
    public double Area() {
        return 3.14 * 5 * 5;
    }
}

medium

A. Circle must declare Area() as override

B. Shape cannot have abstract methods

C. Circle cannot inherit from Shape

D. Area method should return int, not double

Solution

1. Step 1: Check abstract method override rules

   When a class inherits an abstract method, it must override it using the override keyword.

2. Step 2: Identify missing override keyword

   The Circle class defines Area() but misses override, causing a compile error.

3. Final Answer:

   Circle must declare Area() as override -> Option A

4. Quick Check:

   Override keyword required for abstract methods [OK]

Hint: Override abstract methods with 'override' keyword [OK]

Common Mistakes:

• Omitting override keyword
• Thinking abstract methods can be ignored
• Confusing return types

5. You want to design a system where all vehicles must have a method StartEngine(), but the way engines start differs by vehicle type. Which approach is best in C#?

hard

A. Create a static class Vehicle with static StartEngine() method.

B. Create a concrete class Vehicle with a fully implemented StartEngine() method for all vehicles.

C. Use an interface with a concrete StartEngine() method and inherit it in all vehicle classes.

D. Create an abstract class Vehicle with abstract method StartEngine(), then implement it in subclasses.

Solution

1. Step 1: Analyze requirement for different implementations

   Since StartEngine() differs by vehicle type, it should be declared abstract to force subclasses to provide their own version.

2. Step 2: Choose correct class design

   An abstract class Vehicle with an abstract StartEngine() method fits best, allowing subclasses to implement specific behavior.

3. Final Answer:

   Create an abstract class Vehicle with abstract method StartEngine(), then implement it in subclasses. -> Option D

4. Quick Check:

   Abstract class for common plan, concrete for specifics [OK]

Hint: Abstract method for varying behavior, concrete class for details [OK]

Common Mistakes:

• Using concrete class with one method for all vehicles
• Trying to put method body in interface (not allowed)
• Using static class which can't be inherited