Avoid IDE030X suggestions for collection expressions that could change semantics/perf #100250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
e.g. by default this will trigger IDE0300:
but if that's changed to:
the compiler tries to protect the readonly-ness of the enumerable from upcasting and emits something along the lines of:
which is then both an extra allocation and hinders some downstream optimizations from code such as we have in LINQ that tests whether the source is a T[].
Putting this into the .editorconfig prevents the IDE from recommending switching to collection expressions in such cases.