title: In an If-Else Statement for a method return, should an Else be explicitly stated if it can instead be implicitly followed?
body: <p>I have a method that checks certain things and returns a Boolean based on those checks. It involves a single branching If section that checks about 5 conditions in sequence. If any of those conditions return true, then the method will <code>return true;</code>. If none of the conditions return true, then the method will <code>return false;</code>. Since the code after the If section will only run if none of the conditions are true, then that code is logically identical to including an actual Else statement. </p>
  
  <p>So is it a better idea to actually write in the Else statement for this kind of situation?</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>It turns out that I needed information on which condition actually tripped the "true" for some of these, so I changed the method to return an int, with -1 representing the "false" situation. The logic still remains, if none of the conditions are true, it'll return -1. So, I no longer have the condensable option of <code>return (cond1 || cond2 || cond3 || cond4 || cond5);</code>, but I thank everyone for that suggestion too, since I had indeed not thought about it (primarily because cond3 is a very complex condition involving checking for intersection in the midpoints of two pairs of DateTime objects, so it would look ugly). While the nature of the method has changed, the nature of this question has not and all answers are still basically applicable...</p>
  
  <p>The code is currently, to paraphrase it and cut out all the extraneous code that defines cond1 thru cond5...</p>
  
  <pre><code>if (cond1) { return 1; }
  else if (cond2) { return 2; }
  else if (cond3) { return 3; }
  else if (cond4) { return 4; }
  else if (cond5) { return 5; }
  </code></pre>