Click here to Skip to main content
15,888,610 members
Articles / Programming Languages / C# 4.0

Best Practices on Using Implicitly Typed (i.e. var ) and Explicitly Typed Variables

Rate me:
Please Sign up or sign in to vote.
2.68/5 (14 votes)
4 Nov 2009CPOL1 min read 82.4K   5   60
Best practise using var

Introduction

Leveraging the type inference is wonderful when writing code. With the arrival of ‘var’ in C# 3.0, it now allows a developer to write more relaxed code.

int i = 2 can now be written as var i = 2, without having to worry about the overhead for boxing/un-boxing.

The compiler infers the type indicated by ‘var’ from the expression used to initialize the variable, and the IL code contains the inferred type. However, it is not always the best thing to use var. While using ‘var’ can help developers to avoid all the type declarations for local variables, it has an impact on code readability. Consider invoking an overloaded method, which differs in the parameter type. If the method is invoked with parameters declared as ‘var’, it makes the code complex to understand.

Consider the following snippet:

C#
private int GetUserInput()
{
    Random r = new Random(1);
    return r.Next();
}

private int Add(int numberOne, int numberTwo)
{
    return numberOne + numberTwo;
}
private float Add(float numberOne, float numberTwo)
{
    return Convert.ToInt32(numberOne + numberTwo);
}

private void InvokeAdd()
{
    var numberOne = GetUserInput();
    var numberTwo = GetUserInput();
    //...
    var addedNumber = Add(numberOne, numberTwo); //version of ‘Add’ method is not evident
}

Which version of ‘Add’ method is invoked is not evident at the first glance, in the above snippet.
Although the best practices for using ‘var’ cannot be made generic but a little guidance can help in making a conscious choice. Below are a few thoughts on when to use or not to use ‘var’.

  1. Do use ‘var’ to:
    1. Refer anonymous types, e.g.
      C#
      var anonymousType = new { Name = "Dilbert" };
    2. Refer query expressions, e.g.
      C#
      var queryExpression = from c in customers where c.Name == "Dilbert" select c;
    3. Refer complex generic types, e.g.
      C#
      var searchList = new Dictionary<string>();
  2. Do not use ‘var’ to:
    1. Refer known types, e.g.

      C#
      var customer = new Customer(); //Do not use 
      var numberList = new int[] { 1, 2, 3, 4, 5 }; //Do not use.
    2. Refer constants, e.g.

      C#
      var i = 5; //Do not use
    3. Refer simple expression assignments, e.g.

      C#
      var count = customers.Count();//Do not use
      var customerName = customer.Name;//Do not use
    4. Refer variables where types cannot be inferred or where inferred type is not what is intended, e.g.

      C#
      IList<customer> customers = new List<customer />(); //Do not use

      Consider code readability and maintainability while making a choice between ‘var’ and explicit type.

History

  • 4th November, 2009: Initial post

License

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


Written By
Unknown
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions

 
GeneralMy vote of 1 Pin
Björn Friedrich14-Jan-11 5:05
Björn Friedrich14-Jan-11 5:05 
GeneralMy vote of 1 Pin
Richard Deeming12-Nov-09 9:00
mveRichard Deeming12-Nov-09 9:00 
General[My vote of 1] Мethodically, socially and morally incorrect Pin
Sergey Alexandrovich Kryukov9-Nov-09 6:51
mvaSergey Alexandrovich Kryukov9-Nov-09 6:51 
GeneralSuch an overreaction... Pin
CurtainDog9-Nov-09 19:45
CurtainDog9-Nov-09 19:45 
GeneralRe: Such an overreaction... Pin
Sergey Alexandrovich Kryukov10-Nov-09 5:43
mvaSergey Alexandrovich Kryukov10-Nov-09 5:43 
GeneralMy vote of 1 Pin
brian_agnes9-Nov-09 6:04
brian_agnes9-Nov-09 6:04 
GeneralShould be based on facts and reasoning Pin
Sergey Alexandrovich Kryukov9-Nov-09 6:36
mvaSergey Alexandrovich Kryukov9-Nov-09 6:36 
GeneralMy vote of 2 Pin
Ben Robbins8-Nov-09 21:48
Ben Robbins8-Nov-09 21:48 
GeneralRe: My vote of 2 [modified] Pin
ATANU.PODDER8-Nov-09 23:15
ATANU.PODDER8-Nov-09 23:15 
GeneralMy vote of 2 Pin
dequadin7-Nov-09 6:52
dequadin7-Nov-09 6:52 
GeneralRe: My vote of 2 Pin
ATANU.PODDER8-Nov-09 23:27
ATANU.PODDER8-Nov-09 23:27 
GeneralI understand the boxing reference Pin
Member 36807856-Nov-09 5:09
Member 36807856-Nov-09 5:09 
GeneralRe: I understand the boxing reference Pin
dberindei8-Nov-09 22:24
dberindei8-Nov-09 22:24 
GeneralRe: I understand the boxing reference Pin
Member 36807859-Nov-09 6:36
Member 36807859-Nov-09 6:36 
GeneralRe: I understand the boxing reference Pin
dberindei9-Nov-09 21:23
dberindei9-Nov-09 21:23 
Member 3680785 wrote:
Object o = "Hello, World of Warcraft";
Console.WriteLine(o);
o=44;
Console.WriteLine(o);
ArrayList al=new ArrayList();
al.Add(o);


This is precisely not what the var keyword does... try if for yourself, replace Object with var and you'll see that the code no longer compiles.

Console.WriteLine has an overload for int, so it doesn't perform any boxing/unboxing if you call Console.WriteLine(44). In your example the boxing happens in the 'o=44;' line, which I argue very few developers would use. After all, declaring another variable would require just 4 more characters.

Member 3680785 wrote:
The last two statements are particularly revealing. Microsoft was not so anti-boxing back then as they are now. Presumably there were also many early .NET libraries build similarly around "Object," or (in a related but somewhat better strategy) some more specific base class.


Microsoft did care about performance from the beginning, you could always use straight arrays instead of ArrayList. In fact that's how most of the early APIs work.

Member 3680785 wrote:
After a certain point, Microsoft started to care more about performance, and they introduced features designed to move polymorphic operations forward-in-time, from execution-time to compilation-time. Then, they gave us generics (which are still pretty brain-dead compared to C++ template classes), "var," etc.


I don't know what you mean with "moving polymorphic operations forward-in-time", but generics don't do this (they just remove a downcast from Object to your type), and 'var' certainly doesn't do it (since the compiled IL looks exactly the same with or without var - remember that your example does *not* work with var).
GeneralRe: I understand the boxing reference [modified] Pin
Member 368078511-Nov-09 7:45
Member 368078511-Nov-09 7:45 
GeneralRe: I understand the boxing reference Pin
dberindei11-Nov-09 23:04
dberindei11-Nov-09 23:04 
GeneralRe: I understand the boxing reference Pin
Indrora23-Nov-09 16:10
Indrora23-Nov-09 16:10 
GeneralRe: I understand the boxing reference Pin
dberindei23-Nov-09 21:42
dberindei23-Nov-09 21:42 
GeneralRe: I understand the boxing reference Pin
Indrora4-Dec-09 16:12
Indrora4-Dec-09 16:12 
GeneralRe: I understand the boxing reference Pin
dberindei9-Dec-09 2:17
dberindei9-Dec-09 2:17 
GeneralWhy comparing "object" with "var"? Pin
Sergey Alexandrovich Kryukov9-Nov-09 6:33
mvaSergey Alexandrovich Kryukov9-Nov-09 6:33 
GeneralRe: Why comparing "object" with "var"? Pin
Member 368078511-Nov-09 9:39
Member 368078511-Nov-09 9:39 
GeneralRe: Why comparing "object" with "var"? Pin
Sergey Alexandrovich Kryukov11-Nov-09 12:14
mvaSergey Alexandrovich Kryukov11-Nov-09 12:14 
GeneralMy vote of 2 Pin
Utwig6-Nov-09 2:58
Utwig6-Nov-09 2:58 

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.