Question about the usage of "var" instead of real type

[gyoce]

Hello,

I was wondering why there are a lot of "var" usage instead of real type. I mean, i know that in some cases the "var" is okay because you can easily see the type on the right of the '=' but sometimes it's not that easy.

For me there are some cases that justify the use of var :

var x1 = new MyClass(); // You see the "new" on the right
MyClass x2 = new(); // Equivalent (but personally i prefer this one lol)
var x3 = "this is my string"; // It's okay because we see the quotes

I think in terms of code lisibility it's better to use the real type, see below for examples that for me the use of the real type is better for code understanding :

• here 1
• here 2
• here 3
• here 4
• here 5

I think there are some cases that do not justify having "var" :

var x1 = CallToMyFunction();  // Depends on the real name of the method because "CallToMyFunction" is really not a good name but even if the method has a good name i think it's better to have the real type here
var x2 = myOtherVar1 + myOtherVar2; // We could have custom classes that implements the operator+ to return a custom type or a primitive one

If there is a reason or if i'm wrong i would like to know and understand why 😃

Thank you !

[egil]

Hi @gyoce,

In most cases, we are browsing code using an editor/IDE that allows me to hover over the type and see the type if I am unsure. Yes, browsing on GitHub doesn't always give you that options, so you lose some info, and when I am showing code in slides/presentations, I tend to show types explicitly, but not in codebases I am maintaining. In this codebase we are generally following Microsofts/dotnet's coding standards with a few exceptions, and this is pretty much aligned with most code bases I see in .NET.