Skip to content

Conversation

@Muximize
Copy link
Contributor

This fixes #50328.

Question: is the WorkItem referring to the issue still relevant now that the roslyn-analyzers repo is being archived?

cc: @Dean-NC, @geeknoid, @Youssef1313, @ViktorHofer

@ViktorHofer
Copy link
Member

@dotnet/dotnet-analyzers please take a look as well

@Muximize
Copy link
Contributor Author

Muximize commented Sep 9, 2025

@ViktorHofer I was hoping to get this merged in time for .NET 10. Should I retarget to release/10.0.1xx?

@ViktorHofer
Copy link
Member

I recently switched teams. @dotnet/dotnet-analyzers please chime in

Copy link
Member

@stephentoub stephentoub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@stephentoub stephentoub enabled auto-merge (squash) January 5, 2026 18:31
@stephentoub
Copy link
Member

/ba-g deadletter

@stephentoub stephentoub merged commit df428ab into dotnet:main Jan 5, 2026
24 of 26 checks passed
@Muximize Muximize deleted the fix-CA1859 branch January 5, 2026 21:25
@Muximize
Copy link
Contributor Author

Muximize commented Jan 5, 2026

@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. 😅

@stephentoub
Copy link
Member

/backport to release/10.0.2xx

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

Started backporting to release/10.0.2xx (link to workflow run)

@Dean-NC
Copy link

Dean-NC commented Jan 9, 2026

Thanks Stephen and everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CA1859 improperly handles default interface implementations

6 participants