Skip to main content

Implicit and Explicit Conversions in C#

Let's Start by Converting int to long 

Example 1:      

int IntValue = 10;
long LongValue;

// Converting int to long is easy

LongValue = IntValue;
// The above code will work as we are converting from small memory size to bigger one


Example 2:

int IntValue = 10;
long LongValue = 1000;

// Converting int to long is NOT easy possible

IntValue = LongValue;
// The above code will NOT work as we are converting from bigger memory size to smaller one,
// Even though we are assigning the values to int that is capable of holding

Compiler Error:

Cannot implicitly convert type 'long' to 'int'. An explicit conversion exists (are you missing a cast?)



So how do we convert? here comes the explicit conversion technique,

Example 3:

int IntValue = 10;
long LongValue = 1000;

IntValue = (int)LongValue;



This will perfectly work but explicit conversion has some dangers, we will see what are they,

For example if the long holds a value that is more than the int's capability  

Say Here in this example we are adding the long's value as int's MaxValue plus 1 and assign to int by converting,

Example 4: 

This will not produce compile time error or run time error, but the values will be definitely changed and the reliability will be lost in this scenario 


int IntValue = 10;
long LongValue = int.MaxValue;
LongValue++;

IntValue = (int)LongValue;

See the picture for run time values 



By this we came to know that we should not do the explicit conversion without knowing what the actual value is been passed and the memory size of the value.


Another example where the explicit conversion provides wrong answer 


Example 5:


int IntValue = 10;
long LongValue = long.MaxValue;

IntValue = (int)LongValue;

The IntValue is resulted with -1 



(To be continued)

Comments

Popular posts from this blog

Task Parallel Library (TPL) and Akka.NET: Differences

Task Parallel Library (TPL) and Akka.NET are both powerful tools in the .NET ecosystem for handling parallelism and concurrency, but they serve different purposes and use different models of computation. Here are some key differences:s 1.    Actor Model vs Task-Based Model: Akka.NET is built around the actor model, where actors are the fundamental units of computation and they communicate by exchanging messages. TPL, on the other hand, is task-based. It's designed to make developers more productive by simplifying the process of adding parallelism and concurrency to applications. TPL uses tasks (which are independently executing work units) and provides various ways to control and coordinate them. 2.    Fault Tolerance: One of the key features of Akka.NET is its built-in fault tolerance. It has a "let-it-crash" philosophy, where the system is designed to self-heal from errors. If an actor fails, its parent actor can decide on the supervision strategy: either to resta

Extension Methods - Advanced

Here we will see how can we use the Extension Methods in advanced manner in other types Imagine you often need to retrieve items from a List based on a custom criterion that the built-in LINQ methods don't cover. Extension Methods for Lists: Filtering based on Custom Criteria And the output would be   Extending Enums: Displaying Descriptive Strings Output: Extending DateTime: Calculating Age     Output: The code samples can be found at https://github.com/oneananda/C_Sharp_Examples/tree/main/ExtensionMethods