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

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven