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.
Is there a practical difference between .All() and .TrueForAll() when operating on a List? I know that .All() is part of IEnumerable, so why add .TrueForAll()?
From the docs for
List<T>.TrueForAll:So it was added before
Enumerable.All.The same is true for a bunch of other
List<T>methods which work in a similar way to their LINQ counterparts. Note thatConvertAllis somewhat different, in that it has the advantage of knowing that it’s working on aList<T>and creating aList<TResult>, so it gets to preallocate whatever it needs.