title: LINQ: Not Any vs All Don't
body: <p>Often I want to check if a provided value matches one in a list (e.g. when validating):</p>
  
  <pre><code>if (!acceptedValues.Any(v =&gt; v == someValue))
  {
      // exception logic
  }
  </code></pre>
  
  <p>Recently, I've noticed ReSharper asking me to simplify these queries to:</p>
  
  <pre><code>if (acceptedValues.All(v =&gt; v != someValue))
  {
      // exception logic
  }
  </code></pre>
  
  <p>Obviously, this is logically identical, perhaps slightly more readable (if you've done a lot of mathematics), my question is: does this result in a performance hit?</p>
  
  <p>It feels like it should (i.e. <code>.Any()</code> sounds like it short-circuits, whereas <code>.All()</code> sounds like it does not), but I have nothing to substantiate this. Does anyone have deeper knowledge as to whether the queries will resolve the same, or whether ReSharper is leading me astray?</p>