-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix CA1859 improperly handling default interface implementations #50314
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
Conversation
...lysis.NetAnalyzers.UnitTests/Microsoft.NetCore.Analyzers/Performance/UseConcreteTypeTests.cs
Outdated
Show resolved
Hide resolved
|
@dotnet/dotnet-analyzers please take a look as well |
|
@ViktorHofer I was hoping to get this merged in time for .NET 10. Should I retarget to |
|
I recently switched teams. @dotnet/dotnet-analyzers please chime in |
Co-authored-by: Viktor Hofer <[email protected]>
stephentoub
left a comment
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.
Thanks!
|
/ba-g deadletter |
|
@stephentoub Any chance to get this backported to .NET 10 (and 9)? I hope I don't have to wait 1-2 years to benefit from this. 😅 |
|
/backport to release/10.0.2xx |
|
Started backporting to |
|
Thanks Stephen and everyone! |
This fixes #50328.
Question: is the
WorkItemreferring to the issue still relevant now that the roslyn-analyzers repo is being archived?cc: @Dean-NC, @geeknoid, @Youssef1313, @ViktorHofer