Why polymorphism matters in C Sharp (C#) - Visual Breakdown

Concept Flow - Why polymorphism matters

Create base class reference

↓

Assign derived class object

↓

Call method via base reference

↓

Derived class method runs

↓

Program uses different objects interchangeably

Polymorphism lets a base class reference call methods of derived classes, enabling flexible and interchangeable object use.

Execution Sample

C Sharp (C#)

using System;

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

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

This code shows a base class reference calling a derived class method, demonstrating polymorphism.

Execution Table

Step	Action	Object Type	Method Called	Output
1	Create Dog object	Dog	N/A	No output
2	Assign Dog object to Animal reference 'a'	Dog	N/A	No output
3	Call a.Speak()	Dog	Dog.Speak()	Dog barks
4	End of execution	N/A	N/A	Program ends

💡 Method call completes, program ends

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
a	null	null	Dog object	Dog object	Dog object

Key Moments - 2 Insights

Why does calling Speak() on 'a' run Dog's Speak() and not Animal's?

Because 'a' refers to a Dog object and Speak() is virtual and overridden, the runtime calls Dog's Speak() (see execution_table step 3).

Can we assign different derived objects to the same base reference?

Yes, polymorphism allows the base class reference 'a' to hold any derived class object, enabling flexible code reuse.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output when a.Speak() is called at step 3?

A No output

B Animal speaks

C Dog barks

D Compilation error

💡 Hint

Check the 'Output' column in execution_table row for step 3

At which step is the Dog object assigned to the Animal reference 'a'?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Action' column in execution_table for assignment

If we create a Cat class derived from Animal and assign it to 'a', what method runs when calling a.Speak()?

A Animal's Speak()

B Cat's Speak()

C Dog's Speak()

D No method runs

💡 Hint

Polymorphism calls the derived class method of the actual object assigned to 'a'

Concept Snapshot

Polymorphism lets a base class reference hold derived objects.
Calling virtual methods runs the derived class version.
This enables flexible, interchangeable object use.
Use 'virtual' in base and 'override' in derived classes.
It helps write reusable and extendable code.

Full Transcript

Polymorphism is a key idea in programming where a base class reference can point to objects of derived classes. When you call a method on the base reference, the program runs the version of the method from the actual derived object. This lets you write code that works with many types of objects in a flexible way. In the example, an Animal reference 'a' holds a Dog object. Calling a.Speak() runs Dog's Speak method, not Animal's. This happens because Speak is marked virtual in Animal and overridden in Dog. Polymorphism helps you reuse code and add new types easily without changing existing code.

Practice

1. What is the main benefit of polymorphism in C# programming?

easy

A. It forces all classes to have the same properties.

B. It makes the program run faster by using less memory.

C. It prevents any changes to the code once compiled.

D. It allows one method to work with different types of objects.

Solution

1. Step 1: Understand polymorphism concept

   Polymorphism means one method name can work with different object types.

2. Step 2: Identify the main benefit

   This makes code easier to write and maintain by reusing method names for different classes.

3. Final Answer:

   It allows one method to work with different types of objects. -> Option D

4. Quick Check:

   Polymorphism = One method, many types [OK]

Hint: Polymorphism means one method, many object types [OK]

Common Mistakes:

• Thinking polymorphism speeds up code automatically
• Confusing polymorphism with code immutability
• Believing polymorphism forces identical class properties

2. Which of the following is the correct way to declare a method that demonstrates polymorphism in C#?

easy

A. public void Draw() { }

B. public void Draw(int x) { }

C. public virtual void Draw() { }

D. public static void Draw() { }

Solution

1. Step 1: Identify polymorphic method declaration

   In C#, polymorphism is often shown using virtual methods that can be overridden.

2. Step 2: Check method options

   Only 'public virtual void Draw()' allows derived classes to override and show polymorphism.

3. Final Answer:

   public virtual void Draw() { } -> Option C

4. Quick Check:

   Virtual method enables polymorphism [OK]

Hint: Use 'virtual' keyword to enable polymorphism [OK]

Common Mistakes:

• Choosing static methods which cannot be overridden
• Ignoring the virtual keyword for polymorphism
• Confusing method overloading with polymorphism

3. Consider the following C# code:

class Animal { public virtual string Speak() => "..."; }
class Dog : Animal { public override string Speak() => "Woof"; }
class Cat : Animal { public override string Speak() => "Meow"; }

Animal a = new Dog();
Console.WriteLine(a.Speak());

What is the output?

medium

A. Woof

B. ...

C. Meow

D. Compilation error

Solution

1. Step 1: Understand polymorphism with virtual and override

   The variable 'a' is of type Animal but holds a Dog object. The Speak method is virtual and overridden in Dog.

2. Step 2: Determine which Speak method runs

   At runtime, the Dog's Speak method runs, returning "Woof".

3. Final Answer:

   Woof -> Option A

4. Quick Check:

   Virtual method calls overridden version [OK]

Hint: Virtual method calls override in actual object type [OK]

Common Mistakes:

• Expecting base class method output
• Confusing variable type with object type
• Thinking code causes compile error

4. What is wrong with this C# code snippet that tries to use polymorphism?

class Shape { public void Draw() { Console.WriteLine("Shape"); } }
class Circle : Shape { public void Draw() { Console.WriteLine("Circle"); } }

Shape s = new Circle();
s.Draw();

medium

A. Shape cannot be assigned a Circle object.

B. Draw method in Shape should be virtual to enable polymorphism.

C. Circle class must not have a Draw method.

D. Draw method must be static.

Solution

1. Step 1: Check method declarations for polymorphism

   Polymorphism requires the base method to be marked 'virtual' and the derived method to 'override'.

2. Step 2: Identify missing virtual keyword

   Here, Shape's Draw is not virtual, so Circle's Draw hides it but does not override.

3. Final Answer:

   Draw method in Shape should be virtual to enable polymorphism. -> Option B

4. Quick Check:

   Base method must be virtual for polymorphism [OK]

Hint: Base method needs 'virtual' for polymorphism [OK]

Common Mistakes:

• Thinking method hiding equals polymorphism
• Believing derived method must be removed
• Assuming static methods support polymorphism

5. You have a list of different shapes (Circle, Square, Triangle) all inheriting from Shape with a virtual method Draw(). How does polymorphism help you when you want to draw all shapes without checking their types?

hard

A. You can call Draw() on each Shape reference and the correct shape's Draw runs automatically.

B. You must check each shape's type and call its specific Draw method manually.

C. You need to cast each shape to its exact type before calling Draw().

D. You cannot use polymorphism with collections of different shapes.

Solution

1. Step 1: Understand polymorphism with collections

   Polymorphism allows calling the same method on base class references that point to different derived objects.

2. Step 2: Apply to drawing shapes

   Calling Draw() on each Shape in the list runs the correct overridden Draw method for each shape automatically.

3. Final Answer:

   You can call Draw() on each Shape reference and the correct shape's Draw runs automatically. -> Option A

4. Quick Check:

   Polymorphism enables method calls without type checks [OK]

Hint: Call base method; derived version runs automatically [OK]

Common Mistakes:

• Thinking you must check types before calling methods
• Trying to cast objects unnecessarily
• Believing polymorphism doesn't work with lists