Does it matter performance wise if there is an `else` after the first `return`?

Question

I've now seen two different ways to make a boolean returning method:

bool Case1()
{
    if (A)
        return true;
    else
        return false;
}
bool Case2()
{
    if (A)
        return true;
    return false;
}

Which one is faster? Does it make sense to not write else just to save a line, make it clearer, or is there a negligible performance gain?

Answer 1

No.

Even when we look at their IL code, they have the same IL code, so there is no performance difference between them. Use the one which is more readable for you.

.method private hidebysig instance bool  Case1() cil managed
{
  // Code size       9 (0x9)
  .maxstack  1
  .locals init ([0] bool CS$1$0000,
           [1] bool CS$4$0001)
  IL_0000:  nop
  IL_0001:  ldc.i4.0
  IL_0002:  stloc.1
  IL_0003:  ldc.i4.1
  IL_0004:  stloc.0
  IL_0005:  br.s       IL_0007
  IL_0007:  ldloc.0
  IL_0008:  ret
} // end of method Program::Case1

Look at these pieces of code for their performances;

http://ideone.com/8Sc7Ho --> Memory: 33856 kB

http://ideone.com/MrnaAl --> Memory: 33808 kB

So if you use them even 10.000 times, there is nothing to worry about.

Answer 2

The c# compiler should generate the same IL for these two cases, so there should be no difference in performance. You can always view the generated IL if you are curious what actually happens (attempting to teach how to fish).

IMHO, Case1 is easier to read, which is worth something. My second choice would be return A; (as mentioned in some other answers). If A isn't a bool though, there is an implicit conversion which may be confusing in some cases.

I think readability should win unless you can prove with a profiler that you have a problem.