Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When the Linq namespace is imported, it is possible to use both .Count() and .Count (on objects that implement IList for example).
.Count() will call the .Count property, if available, as per:
C# Count() Extension Method Performance
Is it better then to directly use .Count over .Count(), for a (small) performance gain?
Update: interesting performance figures here (1-2 orders of magnitude): Is the Linq Count() faster or slower than List.Count or Array.Length?
My personal preference is to stick with the existing methods and properties if they are available without casting. Therefore I’d use
Count.