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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve performance of polymorphism #42538
Improve performance of polymorphism #42538
Changes from 1 commit
d359119
af01d59
d034ae8
cafef3b
2a545d9
c36687f
8b370ca
d4bdb19
48db4b9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How's test coverage for all these changes? Are we still at 100% for JsonElement/JsonDocument?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only new LOC that isn't hit is this branch: https://github.com/dotnet/runtime/pull/42538/files#diff-8bee6ed7017869dde2a37df1271e0338R612.
This branch is only hit if we expose this functionality publicly (not called from the serializer) since "valueSpan" will never be empty when using a reader instance with the serializer.
So we could remove this branch and add an Assert, but I suggest leaving until we decide on #42755 which at that point we will add tests to cover that.