Why Default interface methods in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could add new features to your code without breaking everything that already works?

The Scenario

Imagine you have several classes that share some common behavior defined by an interface. You want to add a new method to this interface, but now every class that implements it must update their code to include this new method.

The Problem

This manual update is slow and error-prone because you must find and change every class that implements the interface. Missing one class causes bugs. It's like having to rewrite parts of many recipes just because you want to add a new ingredient.

The Solution

Default interface methods let you add new methods with a default implementation directly in the interface. This means existing classes don't have to change unless they want to customize the new method. It's like adding a new optional step to a recipe that cooks can follow if they want, without breaking old recipes.

Before vs After

✗ Before

interface IShape { void Draw(); }
// Adding new method requires all classes to implement it
class Circle : IShape { public void Draw() { } /* must add new method here */ }

✓ After

interface IShape {
  void Draw();
  void Resize() { /* default resize code */ }
}
// Circle class does not need to change unless it wants to override Resize

What It Enables

It enables evolving interfaces without breaking existing code, making software easier to maintain and extend.

Real Life Example

Think of a smartphone app interface that adds a new feature. Default interface methods let developers add this feature without forcing all existing apps to update immediately.

Key Takeaways

Manually updating all classes for interface changes is tedious and risky.

Default interface methods provide a safe default implementation inside interfaces.

This allows interfaces to grow without breaking existing code.

Practice

1. What is the main purpose of default interface methods in C#?

easy

A. Allow interfaces to have method bodies with default behavior

B. Force all implementing classes to override every method

C. Prevent interfaces from having any methods

D. Make interfaces behave like abstract classes

Solution

1. Step 1: Understand interface limitations before default methods

   Interfaces could only declare methods without bodies, forcing all implementations to define them.

2. Step 2: Recognize the role of default interface methods

   Default interface methods allow interfaces to provide a method body, so implementing classes can use or override it.

3. Final Answer:

   Allow interfaces to have method bodies with default behavior -> Option A

4. Quick Check:

   Default interface methods = method bodies in interfaces [OK]

Hint: Default interface methods add bodies to interfaces [OK]

Common Mistakes:

• Thinking interfaces cannot have any method bodies
• Confusing default methods with abstract methods
• Believing all methods must be overridden

2. Which of the following is the correct syntax to declare a default interface method in C#?

easy

A. abstract void Show() { Console.WriteLine("Hello"); }

B. void Show();

C. default void Show() { Console.WriteLine("Hello"); }

D. void Show() => Console.WriteLine("Hello");

Solution

1. Step 1: Recall default method syntax in interfaces

   Default interface methods can have bodies using either block or expression-bodied syntax.

2. Step 2: Identify correct syntax among options

   void Show() => Console.WriteLine("Hello"); uses expression-bodied syntax correctly inside interface method declaration.

3. Final Answer:

   void Show() => Console.WriteLine("Hello"); -> Option D

4. Quick Check:

   Default method syntax = method with body in interface [OK]

Hint: Default methods have bodies, unlike abstract declarations [OK]

Common Mistakes:

• Using 'default' keyword before method
• Omitting method body
• Writing method body without braces or expression syntax

3. What will be the output of this code?

interface IExample { void Show() => Console.WriteLine("Default"); }
class Test : IExample { }
var t = new Test();
t.Show();

medium

A. Runtime error

B. Compilation error: Show() not implemented

C. Default

D. No output

Solution

1. Step 1: Check if class implements Show()

   Class Test does not implement Show(), but interface provides default implementation.

2. Step 2: Understand default method usage

   Since Test inherits IExample, it uses the default Show() method from interface.

3. Final Answer:

   Default -> Option C

4. Quick Check:

   Default method runs if not overridden [OK]

Hint: If not overridden, default interface method runs [OK]

Common Mistakes:

• Assuming missing implementation causes error
• Expecting runtime error without override
• Thinking interface methods can't have bodies

4. Identify the error in this code snippet:

interface ICalc { int Add(int a, int b) => a + b; }
class Calc : ICalc { public int Add(int a, int b); }

medium

A. Missing method body in Calc's Add method

B. Interface cannot have method bodies

C. Calc class must be abstract

D. Add method should be static

Solution

1. Step 1: Check Calc class Add method declaration

   Calc declares Add with a semicolon but no body, which is invalid in a class.

2. Step 2: Understand method implementation requirements

   Class methods must have bodies unless abstract; here Add is not abstract, so body is required.

3. Final Answer:

   Missing method body in Calc's Add method -> Option A

4. Quick Check:

   Class methods need bodies unless abstract [OK]

Hint: Class methods need bodies unless marked abstract [OK]

Common Mistakes:

• Thinking interface can't have bodies
• Forgetting to add method body in class
• Assuming method should be static

5. Given this interface and classes:

interface ILogger { void Log(string msg) => Console.WriteLine($"Log: {msg}"); }
class FileLogger : ILogger { public void Log(string msg) => Console.WriteLine($"File: {msg}"); }
class ConsoleLogger : ILogger { }

What will be the output of:

ILogger logger1 = new FileLogger();
ILogger logger2 = new ConsoleLogger();
logger1.Log("Test1");
logger2.Log("Test2");

hard

A. File: Test1
File: Test2

B. File: Test1
Log: Test2

C. Log: Test1
Log: Test2

D. Compilation error

Solution

1. Step 1: Analyze FileLogger's Log method

   FileLogger overrides Log to print "File: {msg}".

2. Step 2: Analyze ConsoleLogger's Log method

   ConsoleLogger does not override Log, so uses interface default "Log: {msg}".

3. Step 3: Predict output for each logger

   logger1.Log("Test1") prints "File: Test1"; logger2.Log("Test2") prints "Log: Test2".

4. Final Answer:

   File: Test1 Log: Test2 -> Option B

5. Quick Check:

   Override changes output; default runs if no override [OK]

Hint: Override changes output; default runs if no override [OK]

Common Mistakes:

• Assuming both use default method
• Expecting compilation error due to default method
• Confusing which method runs