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
Migrate CacheFileFormat to System.Text.Json #6081
base: dev
Are you sure you want to change the base?
Migrate CacheFileFormat to System.Text.Json #6081
Changes from all commits
aad148e
e3823cb
179bd18
75ad105
7bf9b8e
a6aed78
cc13dd6
6aa1c4e
655b5f0
6a6d8cb
3956ece
3135134
f79c1a7
6280326
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.
Regarding https://github.com/NuGet/NuGet.Client/pull/6081/files#r1825078556, we lose about 30% perf needing to go though an additional converter:
code
We lose even more perf calling
JsonSerializer.Deserialize
from the converter, rather than my suggestion above, getting the converter directly from options, and calling the converter.It depends on how much we want to microoptimize restore. 30 nanoseconds per project, on my machine, but nanoseconds are super small. Is it worth the public API breaking changes for it? Probably not. But I still think that
IAssetsLogMessage
doesn't have a reason to exist.But I think the additional 60 nanoseconds lost by using
JsonSerializer.Deserialize
is not worth the 1 line of code it saves over getting the converter directly.