implicit operator with generic not working for interface

by

Short answer:

User-defined implicit conversions do not work on interfaces. Don’t try to make it work. Find another solution to your type system problem.

Long answer:

This is a deliberate decision of the C# design team. The principle is that when you are making a conversion involving an interface you want to preserve referential identity; you are asking about the identity of the object that implements the interface, not trying to create a similar object that has similar properties.

The larger principle here is that a user-defined conversion should not replace a built-in conversion. But since almost any class can be subclassed, and that subclass can implement just about any interface, it is very hard to know statically whether a given user-defined conversion involving an interface might be replacing a built-in conversion.

FYI this is a particularly tricky bit of the specification, and the C# compiler has some bugs here. I suspect that one of your cases above takes advantage of these bugs; the fact that there are real-world programs which do so is what prevented me from fixing the bugs.

The bugs are mostly a consequence of this feature being designed before generics, and then not redesigned sufficiently after generics introduced many unforeseen complications.

For details, see my extensive comments here, particularly the bits marked DELIBERATE SPEC VIOLATION that describe problems with interface conversions.

https://github.com/dotnet/roslyn/blob/master/src/Compilers/CSharp/Portable/Binder/Semantics/Conversions/UserDefinedImplicitConversions.cs

As you can see, this file is less than a thousand lines long, and probably more than half comments. It took weeks of careful research and many discussions with the language team to get these semantics sorted out. Once you make a mistake in a compiler, you often have to understand it thoroughly a decade later, and then enshrine it forever so as to not break a customer on upgrade. There are many object lessons to language designers in how C# messed up this obscure part of the specification.

How could I refactor MyClass so it would be possible to work with objects when only the interface is known?

Don’t try. Cast the interface reference to the actual runtime type and then work with it from there. Or create an instance of the desired type explicitly, rather than by implicit conversion. Don’t try to play games with implicit conversions and interfaces; it will not work out well.

More Related Contents:

  1. implicit operator using interfaces
  2. Why does a generic type constraint result in a no implicit reference conversion error?
  3. How to capture value OOPS & Generic [closed]
  4. Create Generic method constraining T to an Enum
  5. Why can’t the C# constructor infer type?
  6. Can’t operator == be applied to generic types in C#?
  7. Nullable type as a generic parameter possible?
  8. Generic constraint to match numeric types [duplicate]
  9. Generic Method Executed with a runtime type [duplicate]
  10. Null or default comparison of generic argument in C#
  11. Combination of List
  12. c# covariant return types utilizing generics
  13. Passing a single item as IEnumerable
  14. Static Generic Class as Dictionary
  15. Get a generic method without using GetMethods
  16. Anonymous Types – Are there any distingushing characteristics?
  17. C# Get Generic Type Name
  18. T must be contravariantly valid
  19. How to Pass Parameters to Activator.CreateInstance()
  20. Practical advantage of generics vs interfaces
  21. C#: System.Object vs Generics
  22. Understanding C# generics much better
  23. How can I get the correct text definition of a generic type using reflection?
  24. What’s Wrong with an ArrayList?
  25. Implementing arithmetic in generics?
  26. How can I register a generic decorator using Castle Windsor?
  27. In C# 4.0, is it possible to derive a class from a generic type parameter?
  28. Intercept async method that returns generic Task via DynamicProxy
  29. How to write this EF Mock setup code as a reusable Generic Boilerplate?
  30. .NET Managing Layers Relationships

Leave a Comment