-
Notifications
You must be signed in to change notification settings - Fork 4k
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
More classification perf fixes. #73535
More classification perf fixes. #73535
Conversation
src/Workspaces/CSharp/Portable/Classification/SyntaxClassification/NameSyntaxClassifier.cs
Outdated
Show resolved
Hide resolved
…tion/NameSyntaxClassifier.cs
…i/roslyn into classificationExt2
typeof(IdentifierNameSyntax), | ||
typeof(QualifiedNameSyntax), | ||
typeof(SimpleNameSyntax), | ||
typeof(GenericNameSyntax), |
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.
no need to check these other 'composed name types'. We only care about X
and X<...>
(and we only classifiy the 'X' part of each). Every other name type composes into one of these two name types that we actually classify here.
this addresses a lot of callbacks for dotted names that serve no purpose.
]; | ||
|
||
protected override int? GetRightmostNameArity(SyntaxNode node) |
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.
unused method.
src/Workspaces/CSharp/Portable/Classification/SyntaxClassification/NameSyntaxClassifier.cs
Outdated
Show resolved
Hide resolved
…tion/NameSyntaxClassifier.cs
@ToddGrun tiny mop up. ONe moer PR coming. Will not be doing obsolete-classification when doing FAR. It is nearly 7% of the scenario: |
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.
Span change is to address this:
Have commented the rest.