Uses existing JSON primitive collection instead of creating a new one #31282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndriySvyryd
approved these changes
Jul 17, 2023
| } | ||
| } | ||
|
|
||
| var listOfT = typeof(List<>).MakeGenericType(elementType); |
There was a problem hiding this comment.
Is there an issue tracking making the concrete type configurable?
There was a problem hiding this comment.
I don't think so.
|
Superseded by #31272 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #30677
Builds on #31272
This is the case where the CLR types contains, for example, an
ObservableCollection<int>. In this case, we populate this existing collection, rather than creating a new instance.Same still needs to be done for relational materialization of primitive collections.