I appreciate what you're trying to do here, but I'm really not motivated to make these changes. Can you help me understand why you believe this is important? If you derive from List<T>, you can't override any of its meaningful methods; anyone who's changing behavior in a derived type's IEnumerable<T> implementation can't have any expectations about how a consumer uses that instance and which behaviors will be employed, as it will change based on how the instance is consumed.

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

This pull request has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

@xtqqczze As with #118682, I'm closing this without merge. If there's a challenge introduced with the current behavior that you think should be addressed, please file an issue where we can discuss the trade-offs.

Generally speaking, behavioral changes need to be agreed upon in an issue before a PR. Thank you for the contributions though.