Backport #78136 to .NET 7 #84936
Merged
Backport #78136 to .NET 7 #84936
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
* Use ForAttributeWithMetadataName instead of CreateSyntaxProvider * Remove unused code * Update export generator too
This comment was marked as outdated.
This comment was marked as outdated.
CyrusNajmabadi
approved these changes
Apr 17, 2023
RikkiGibson
approved these changes
Apr 17, 2023
jeffschwMSFT
approved these changes
Apr 17, 2023
This was referenced Apr 17, 2023
pavelsavara
approved these changes
Apr 18, 2023
lewing
approved these changes
Apr 18, 2023
sharwell
added a commit
to sharwell/roslyn
that referenced
this pull request
Apr 24, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
main PR #78136
Description
The JSImportGenerator and JSExportGenerator are causing VS performance issues due to not using more efficient APIs that Roslyn introduced in VS 17.4.
Customer Impact
Visual Studio experiences large amounts of allocations that show up in VS performance traces. #78136 (comment)
Regression
This is not a regression.
Testing
This change has been in .NET 8 for months, and very similar changes have been applied to other similar generators in .NET 7 since before release.
Risk
Low risk. This change is very mechanical and follows an established pattern to convert to using the new API and has been working in main for months.
Package authoring signed off?
N/A
IMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.