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.
IF all my methods, need to expose a collection, then I need to user the Linq Extension .ToList(), almost everywhere I need to use lists, or user Collections in all my code.
If that’s the case, .ToList() is ignoring the rule right? Or is there a technique like copying the list o something to fix the violation and still return a list?
I disable that rule because I don’t feel like it’s a valid one. If you want to return a collection which contains an
O(1)count and is not a direct reference to an internal field,List<T>is the best choice.I don’t deeply understand your case here but it sounds like you have a method which returns a LINQ query over some internal data. If that’s the case then using a
.ToList()on the data is appropriate since you likely don’t want future modifications of your internal fields to affect the return value of a method. In that case, there is no reason to not expose it as aList<T>.