| ▲ | bob1029 2 days ago | ||||||||||||||||
> There’s no reason to do ToList there In this case, I would move it to the very end if we are concerned about the underlying data shifting when the collection is actually enumerated. Forgetting to materialize LINQ results can cause a lot of trouble, oftentimes in ways that happily evade detection while a debugger is attached. | |||||||||||||||||
| ▲ | klysm 2 days ago | parent [-] | ||||||||||||||||
> if we are concerned about the underlying data shifting when the collection is actually enumerated I’m not sure what you mean by this. You can fulfill the IEnumerable contract without allowing multiple enumerations, but that doesn’t really have to do with the data shifting around. Doing ToList can be an expensive and unnecessary allocation | |||||||||||||||||
| |||||||||||||||||