Bird
Raised Fist0
C Sharp (C#)programming~5 mins

Virtual method dispatch mechanism in C Sharp (C#) - Time & Space Complexity

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Time Complexity: Virtual method dispatch mechanism
O(1)
Understanding Time Complexity

When a program calls a virtual method, it decides at runtime which version to run. This process is called virtual method dispatch.

We want to understand how the time to find and run the right method changes as the program grows.

Scenario Under Consideration

Analyze the time complexity of calling a virtual method in a class hierarchy.


public class Animal {
    public virtual void Speak() {
        Console.WriteLine("Animal sound");
    }
}

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

Animal pet = new Dog();
pet.Speak();
    

This code calls a virtual method Speak on an object that is actually a Dog. The program must find the right Speak method to run.

Identify Repeating Operations

Virtual method dispatch involves looking up the method to call at runtime.

  • Primary operation: Accessing the method table (vtable) to find the correct method.
  • How many times: Once per virtual method call.
How Execution Grows With Input

The time to dispatch a virtual method call stays about the same no matter how many classes or methods exist.

Input Size (number of classes)Approx. Operations
101 method lookup
1001 method lookup
10001 method lookup

Pattern observation: The lookup time does not grow with the number of classes; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means the time to find and call the right method stays the same no matter how many classes or methods there are.

Common Mistake

[X] Wrong: "Virtual method calls take longer as the number of classes grows because the program searches through all classes."

[OK] Correct: The program uses a direct lookup table, so it finds the method quickly without searching through all classes.

Interview Connect

Understanding virtual method dispatch helps you explain how object-oriented programs run efficiently. It shows you know how programs handle flexible behavior without slowing down.

Self-Check

"What if the program used a different method lookup strategy that searched classes one by one? How would the time complexity change?"

Practice

(1/5)
1. What does the virtual method dispatch mechanism in C# primarily allow?
virtual methods let child classes provide their own version of a method. What is the main benefit?
easy
A. It forces the program to call the base class method only.
B. It makes all methods static by default.
C. It disables method overriding in child classes.
D. It allows the program to decide at runtime which method version to call.

Solution

  1. Step 1: Understand virtual method purpose

    Virtual methods allow child classes to override a method and provide their own implementation.
  2. Step 2: Identify when method is chosen

    The actual method called is decided at runtime, based on the object's real type, not the variable's type.
  3. Final Answer:

    It allows the program to decide at runtime which method version to call. -> Option D
  4. Quick Check:

    Virtual method dispatch = runtime method choice [OK]
Hint: Virtual means runtime method choice, not compile-time [OK]
Common Mistakes:
  • Thinking method is fixed at compile time
  • Confusing virtual with static methods
  • Assuming base method always runs
2. Which of the following is the correct syntax to declare a virtual method in a C# class?
easy
A. virtual public void Display() { }
B. public void virtual Display() { }
C. public virtual void Display() { }
D. public override void Display() { }

Solution

  1. Step 1: Recall virtual method syntax

    The keyword virtual comes after the access modifier and before the return type and method name.
  2. Step 2: Check each option

    public virtual void Display() { } matches correct syntax: public virtual void Display() { }. Options B and C have wrong order, D uses override which is for overriding, not declaring virtual.
  3. Final Answer:

    public virtual void Display() { } -> Option C
  4. Quick Check:

    virtual keyword after access modifier [OK]
Hint: virtual keyword goes right after access modifier [OK]
Common Mistakes:
  • Placing virtual after method name
  • Using override instead of virtual to declare
  • Wrong keyword order
3. Consider the following code:
class Base {
    public virtual string GetName() => "Base";
}
class Derived : Base {
    public override string GetName() => "Derived";
}

Base obj = new Derived();
Console.WriteLine(obj.GetName());

What will be the output?
medium
A. Base
B. Derived
C. Compile-time error
D. Runtime exception

Solution

  1. Step 1: Identify method overriding

    The Derived class overrides the virtual method GetName from Base.
  2. Step 2: Understand virtual dispatch

    The variable obj is of type Base but holds a Derived object. Virtual dispatch calls the Derived version at runtime.
  3. Final Answer:

    Derived -> Option B
  4. Quick Check:

    Virtual method calls child's override [OK]
Hint: Virtual calls run child's method if overridden [OK]
Common Mistakes:
  • Assuming base method runs due to variable type
  • Confusing compile-time and runtime binding
  • Expecting errors from override
4. What is wrong with this code snippet?
class Animal {
    public virtual void Speak() {
        Console.WriteLine("Animal speaks");
    }
}
class Dog : Animal {
    public void Speak() {
        Console.WriteLine("Dog barks");
    }
}

Animal a = new Dog();
a.Speak();
medium
A. Dog's Speak method should be marked override to override base virtual method.
B. Animal's Speak method should not be virtual.
C. Dog's Speak method should be static.
D. No error; code runs and prints "Dog barks".

Solution

  1. Step 1: Check method overriding rules

    To override a virtual method, the child method must use override keyword.
  2. Step 2: Analyze given code

    Dog's Speak method lacks override, so it hides base method instead of overriding. Virtual dispatch calls base method.
  3. Final Answer:

    Dog's Speak method should be marked override to override base virtual method. -> Option A
  4. Quick Check:

    Override keyword needed to override virtual method [OK]
Hint: Override keyword required to override virtual method [OK]
Common Mistakes:
  • Forgetting override keyword in child method
  • Assuming method hides base automatically
  • Confusing virtual and override keywords
5. You have a base class Shape with a virtual method Draw(). Two derived classes Circle and Square override Draw(). You want to write a method that takes a list of Shape objects and calls Draw() on each, ensuring the correct derived method runs.

Which approach correctly uses virtual method dispatch to achieve this?
hard
A. Declare Draw() as virtual in Shape, override in derived classes, then call Draw() on each Shape reference in the list.
B. Declare Draw() as static in Shape and call it directly on the class.
C. Do not use virtual; instead, use type checking and cast each object to call the correct method.
D. Override Draw() in derived classes but call Shape.Draw() explicitly for all objects.

Solution

  1. Step 1: Understand virtual method usage

    Declaring Draw() as virtual in base allows derived classes to override it.
  2. Step 2: Use polymorphism in list iteration

    Calling Draw() on each Shape reference triggers virtual dispatch, running the correct derived method.
  3. Final Answer:

    Declare Draw() as virtual in Shape, override in derived, call Draw() on each Shape reference. -> Option A
  4. Quick Check:

    Virtual + override + call on base type = correct method run [OK]
Hint: Use virtual + override, call on base type for correct method [OK]
Common Mistakes:
  • Using static methods which don't support polymorphism
  • Manually casting instead of relying on virtual dispatch
  • Calling base method explicitly ignoring overrides