Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

User-defined conversion operator from base class

Tags:

c#

casting

Introduction

I am aware that "user-defined conversions to or from a base class are not allowed". MSDN gives, as an explanation to this rule, "You do not need this operator."

I do understand that an user-defined conversion to a base class is not needed, as this obviously done implicitly. However, I do need a conversion from a base class.

In my current design, a wrapper of unmanaged code, I use a pointer, stored in an Entity class. All the classes using a pointer derive from that Entity class, for example, a Body class.

I therefore have:

Method A

class Entity {     IntPtr Pointer;      Entity(IntPtr pointer)     {         this.Pointer = pointer;     } }  class Body : Entity {     Body(IntPtr pointer) : base(pointer) { }      explicit operator Body(Entity e)     {         return new Body(e.Pointer);     } } 

This cast is the illegal one. (Note that I didn't bother writing the accessors). Without it, the compiler will allow me to do:

Method B

(Body)myEntity ... 

However, at runtime, I will get an exception saying this cast is impossible.

Conclusion

Therefore here I am, needing an user-defined conversion from a base class, and C# refuses it to me. Using method A, the compiler will complain but the code would logically work at runtime. Using method B, the compiler will not complain but the code will obviously fail at runtime.

What I find strange in this situation is that MSDN tells me I do not need this operator, and the compiler acts as if it was possible implicitly (method B). What am I supposed to do?

I am aware that I can use:

Solution A

class Body : Entity {     Body(IntPtr pointer) : base(pointer) { }      static Body FromEntity(Entity e)     {         return new Body(e.Pointer);     } } 

Solution B

class Body : Entity {     Body(IntPtr pointer) : base(pointer) { }      Body(Entity e) : base(e.Pointer) { } } 

Solution C

class Entity {     IntPtr Pointer;      Entity(IntPtr pointer)     {         this.Pointer = pointer;     }      Body ToBody()     {         return new Body(this.Pointer);     } } 

But honestly, all the syntaxes for these are horrible and should in fact be casts. So, any way to make the casts work? Is it a C# design flaw or did I miss a possibility? It's as if C# didn't trust me enough to write my own base-to-child conversion using their cast system.

like image 990
Lazlo Avatar asked Aug 03 '10 21:08

Lazlo


People also ask

What is user-defined conversion?

For more information, see Standard Conversions. User-defined conversions perform conversions between user-defined types, or between user-defined types and built-in types. You can implement them as Conversion constructors or as Conversion functions.

What is user-defined conversion in C++?

User-defined conversions allow you to specify object conversions that are implicitly applied by the compiler, in addition to standard built-in type conversions.

How many types are there in user-defined conversion from class to class?

There are two types of user-defined conversions: Conversion constructors and conversion functions.

How many types are there in user-defined conversion question?

Explanation: There are two types of user-defined conversions. They are conversion by the constructor, Conversion functions.


2 Answers

It's not a design flaw. Here's why:

Entity entity = new Body(); Body body = (Body) entity; 

If you were allowed to write your own user-defined conversion here, there would be two valid conversions: an attempt to just do a normal cast (which is a reference conversion, preserving identity) and your user-defined conversion.

Which should be used? Would you really want is so that these would do different things?

// Reference conversion: preserves identity Object entity = new Body(); Body body = (Body) entity;  // User-defined conversion: creates new instance Entity entity = new Body(); Body body = (Body) entity; 

Yuk! That way madness lies, IMO. Don't forget that the compiler decides this at compile-time, based only on the compile-time types of the expressions involved.

Personally I'd go with solution C - and possibly even make it a virtual method. That way Body could override it to just return this, if you want it to be identity preserving where possible but creating a new object where necessary.

like image 160
Jon Skeet Avatar answered Oct 05 '22 06:10

Jon Skeet


Well, when you are casting Entity to Body, you are not really casting one to another, but rather casting the IntPtr to a new entity.

Why not create an explicit conversion operator from IntPtr?

public class Entity {     public IntPtr Pointer;      public Entity(IntPtr pointer) {         this.Pointer = pointer;     } }  public class Body : Entity {     Body(IntPtr pointer) : base(pointer) { }      public static explicit operator Body(IntPtr ptr) {         return new Body(ptr);     }      public static void Test() {         Entity e = new Entity(new IntPtr());         Body body = (Body)e.Pointer;     } } 
like image 29
Igor Zevaka Avatar answered Oct 05 '22 05:10

Igor Zevaka