Why are C# 4 optional parameters defined on interface not enforced on implementing class?

by

UPDATE: This question was the subject of my blog on May 12th 2011. Thanks for the great question!

Suppose you have an interface as you describe, and a hundred classes that implement it. Then you decide to make one of the parameters of one of the interface’s methods optional. Are you suggesting that the right thing to do is for the compiler to force the developer to find every implementation of that interface method, and make the parameter optional as well?

Suppose we did that. Now suppose the developer did not have the source code for the implementation:

// in metadata:
public class B 
{ 
    public void TestMethod(bool b) {}
}

// in source code
interface MyInterface 
{ 
    void TestMethod(bool b = false); 
}
class D : B, MyInterface {}
// Legal because D's base class has a public method 
// that implements the interface method

How is the author of D supposed to make this work? Are they required in your world to call up the author of B on the phone and ask them to please ship them a new version of B that makes the method have an optional parameter?

That’s not going to fly. What if two people call up the author of B, and one of them wants the default to be true and one of them wants it to be false? What if the author of B simply refuses to play along?

Perhaps in that case they would be required to say:

class D : B, MyInterface 
{
    public new void TestMethod(bool b = false)
    {
        base.TestMethod(b);
    }
}

The proposed feature seems to add a lot of inconvenience for the programmer with no corresponding increase in representative power. What’s the compelling benefit of this feature which justifies the increased cost to the user?

UPDATE: In the comments below, supercat suggests a language feature that would genuinely add power to the language and enable some scenarios similar to the one described in this question. FYI, that feature — default implementations of methods in interfaces — will be added to C# 8.

More Related Contents:

  1. C# 4.0, optional parameters and params do not work together
  2. method overloading vs optional parameter in C# 4.0 [duplicate]
  3. C# Interfaces. Implicit implementation versus Explicit implementation
  4. Understanding Covariant and Contravariant interfaces in C#
  5. What is the ‘dynamic’ type in C# 4.0 used for?
  6. Interfaces — What’s the point?
  7. How do arrays in C# partially implement IList?
  8. What are the true benefits of ExpandoObject?
  9. Parse Math Expression [duplicate]
  10. C# Create New T()
  11. Does Parallel.ForEach limit the number of active threads?
  12. implicit vs explicit interface implementation [duplicate]
  13. creating WCF ChannelFactory
  14. Should you declare methods using overloads or optional parameters in C# 4.0?
  15. C# 4.0: Can I use a TimeSpan as an optional parameter with a default value?
  16. Why is AddRange faster than using a foreach loop?
  17. When is using the C# ref keyword ever a good idea?
  18. How to check if a user belongs to an AD group?
  19. Why are interfaces not [Serializable]?
  20. Does the System.Windows.Forms.Timer run on a different thread than the UI?
  21. How can I implement static methods on an interface?
  22. C# operator overload for `+=`?
  23. Dynamically implementing an interface in .NET 4.0 (C#)
  24. How to pass a nullable type to a P/invoked function [duplicate]
  25. How to get current working directory path c#?
  26. How does a generic constraint prevent boxing of a value type with an implicitly implemented interface?
  27. How to get content type of a web address?
  28. C#: Default implementation for == and != operators for objects
  29. What exactly is “interface based programming”?
  30. Does VLC media player have a C# interface? [closed]

Leave a Comment