Click here to Skip to main content
15,883,975 members
Articles / Programming Languages / C# 3.5

Type conversions with implicit and explicit operators

Rate me:
Please Sign up or sign in to vote.
4.65/5 (22 votes)
12 Apr 2011CPOL4 min read 129.2K   20   18
This article helps to understand how to do user defined type conversions using implicit and explicit operators.

Introduction

In this article, I'm going to describe how to use type conversion operators (implicit and explicit) in user-defined classes. We commonly come across situations in which the same real-world entity is represented in two different classes. For example, when integrating two sub-systems into one, we see an entity is represented as Author in one sub-system and as Writer in the other. Although in the combined system both represents the same real-world object, it is difficult to represent them as one throughout because of the extensive code change and dependencies.

In these situations, normally when the objects move between systems, at one point, we have to convert the Author to Writer and vice-versa. Usually we go ahead and create helper classes or extension methods to convert one into the other. But in this article, I'm going to show you how we can use the implicit/explicit operators to make the conversions (Author to Writer or Writer to Author) more easy!

Background

Casting

Conversion between data types can be done in two ways by casting:

  • Implicit casting
  • Explicit casting

Implicit casting

Implicit casting doesn't require a casting operator. This casting is normally used when converting data from smaller integral types to larger or derived types to the base type.

C#
int x = 123;
double y = x;

In the above statement, the conversion of data from int to double is done implicitly, in other words programmer don't need to specify any type operators.

Explicit casting

Explicit casting requires a casting operator. This casting is normally used when converting a double to int or a base type to a derived type.

C#
double y = 123;
int x = (int)y;

In the above statement, we have to specify the type operator (int) when converting from double to int else the compiler will throw an error. You can learn more about casting here.

Conversion operators

Conversion operators help to cast user-defined types from one to the other much like the basic types. For implicit or explicit conversion, we have to create a static method in the corresponding class with method name as the type it returns including the keyword that says implicit or explicit. To know more, follow this link.

Let's see an example!

Let's see an example of how we can implement the casting mechanism in our user-defined classes using conversion operators.

C#
public class Author
{
    public string First;
    public string Last;
    public string[] BooksArray;
}

public class Writer
{
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public List<string> Books { get; set; }
}

We have two classes Author and Writer used in different sub-systems that represent the same real-world entity. Let's see how we can implement implicit or explicit casting in the classes.

C#
Author author2 = (Author)writer; //explicit casting 
Author author1 = writer; //implicit casting

First, let's try explicit casting,

  • Create a static method in the Author class. The name of the method should be the same as the type it's going to be casted; in our case, it is Writer. For explicit casting, we need the explicit keyword to be included in the method definition.
  • C#
    public static explicit operator Writer(Author a)
    {
        //implementation goes here..
    }
  • Create an instance of the Writer class and populate its fields from the passed Author instance.
  • C#
    public static explicit operator Writer(Author a)
    {
        return new Writer
        {
            FirstName = a.First,
            LastName = a.Last,
            Books = a.BooksArray != null ? a.BooksArray.ToList() : null
        };
    }

That's it! Now wherever we need to cast Author to Writer explicitly, it's as simple as shown below:

C#
Author a = new Author
{
    First = "Vijaya",
    Last = "Anand",
    BooksArray = new string[] { "book1" }
};
Writer w = (Writer)a; //explicitly casting from Author to Writer.

To cast the Writer instance back to Author, we can have another static method having the name Author.

C#
public static explicit operator Author(Writer w)
{
    return new Author
    {
        First = w.FirstName,
        Last = w.LastName,
        BooksArray = w.Books != null ? w.Books.ToArray() : null
    };
}

For implicit casting, we have to follow the same steps as above except we have to use the implicit keyword instead of explicit.

C#
public static implicit operator Writer(Author a)
{
    return new Writer
    {
        FirstName = a.First,
        LastName = a.Last,
        Books = a.BooksArray != null ? a.BooksArray.ToList() : null
    };
}

Now implicit casting is as simple as:

C#
Author a = new Author
{
    First = "Vijaya",
    Last = "Anand",
    BooksArray = new string[] { "book1" }
};
Writer w = a; //implicitly casting from Author to Writer.

Whenever we do implicit or explicit casting, the corresponding static method will be called.

Summary

After playing around with implicit and explicit casting in user-defined types for a while, I would like to summarize some points I learnt:

  1. We can have the conversion operator methods in any class. For example, if you create a static method that casts Author to Writer, that can be located in either the Author class or the Writer class.
  2. We can't have both explicit and implicit operator methods for casting the same type to another. For example, if you already created a method for explicit casting from Author to Writer, you can't have another method for casting implicitly from Author to Writer.
  3. The implicit conversion method can also be used for explicit. For example, if there is an implicit conversion method that converts Author to Writer and you are explicitly casting Author to Writer, the casting still works.

That's all! Hope you enjoyed it. Please drop your comments and votes.

History

  • 12 April - Added History section.
  • 7 April - Added Summary section.
  • 6 April - Fixed the static field issue.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Software Developer Trigent Software Private Limited
India India
I'm a software developer from south tip of India. I spent most of the time in learning new technologies. I've a keen interest in client-side technologies especially JavaScript and admire it is the most beautiful language ever seen.

I like sharing my knowledge and written some non-popular articles. I believe in quality and standards but blames myself for lagging them.

I believe in small things and they makes me happy!

Comments and Discussions

 
Generaltype casting Pin
extremjava24-Aug-14 15:35
extremjava24-Aug-14 15:35 
GeneralMy vote of 3 Pin
Sabarish R L6-Jul-14 11:53
Sabarish R L6-Jul-14 11:53 
QuestionDie Abnehm Lösung Pin
serchenry27-Dec-13 15:05
serchenry27-Dec-13 15:05 
GeneralMy vote of 5 Pin
RADHIKA SUBBU12-Aug-12 6:30
RADHIKA SUBBU12-Aug-12 6:30 
GeneralMy vote of 3 Pin
ervegter6-Apr-11 5:13
ervegter6-Apr-11 5:13 
GeneralRe: My vote of 3 Pin
After20506-Apr-11 19:12
After20506-Apr-11 19:12 
GeneralMy vote of 3 Pin
John Brett5-Apr-11 21:49
John Brett5-Apr-11 21:49 
GeneralRe: My vote of 3 Pin
JV99995-Apr-11 22:00
professionalJV99995-Apr-11 22:00 
GeneralRe: My vote of 3 Pin
After20505-Apr-11 22:27
After20505-Apr-11 22:27 
GeneralRe: My vote of 3 Pin
JV99995-Apr-11 22:30
professionalJV99995-Apr-11 22:30 
GeneralRe: My vote of 3 Pin
After20505-Apr-11 22:45
After20505-Apr-11 22:45 
GeneralRe: My vote of 3 Pin
JV99995-Apr-11 23:23
professionalJV99995-Apr-11 23:23 
GeneralRe: My vote of 3 Pin
After20505-Apr-11 23:51
After20505-Apr-11 23:51 
GeneralRe: My vote of 3 Pin
JV99996-Apr-11 1:27
professionalJV99996-Apr-11 1:27 
GeneralRe: My vote of 3 Pin
John Brett5-Apr-11 22:54
John Brett5-Apr-11 22:54 
OK, so now I think I understand your reasoning. However, you're working on the assumption that there will only ever be one Author, and breaking the Principle of least astonishment (you are changing the semantics of casts)

An example of how to make it all go wrong:
Author a = new Author
{
    First = "Vijaya",
    Last = "Anand",
    BooksArray = new string[] { "book1" }
};
Author b = new Author
{
    First = "John",
    Last = "Brett",
    BooksArray = new string[] { "autobiography" }
};
Writer wa = a; //implicitly casting from Author to Writer.
Console.Out.WriteLine("Writer A is {0} {1}", wa.FirstName, wa.LastName);

Writer wb = b; //implicitly casting from Author to Writer.

Console.Out.WriteLine("Writer A is {0} {1}", wa.FirstName, wa.LastName);
Console.Out.WriteLine("Writer B is {0} {1}", wb.FirstName, wb.LastName);


Output
Writer A is Vijaya Anand
Writer A is John Brett
Writer B is John Brett


Casting is the wrong solution to architectural issues about the potential linkage between different objects, but that's a whole different discussion.

It is a false economy to try to save the memory allocations because small memory allocations of this kind just isn't that big a deal in .Net. Its far more important for the code to be correct.

If your examples were using structs, then the issue would be different, and you wouldn't have this linkage between the two returned objects (although you still wouldn't actually be saving much in terms of allocations).
GeneralRe: My vote of 3 Pin
After20505-Apr-11 23:05
After20505-Apr-11 23:05 
GeneralRe: My vote of 3 Pin
John Whitmire12-Apr-11 3:24
professionalJohn Whitmire12-Apr-11 3:24 
GeneralRe: My vote of 3 Pin
After205012-Apr-11 6:31
After205012-Apr-11 6:31 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.