Dispose
extension methods should not even be considered in pattern-based disposal
#32767
Labels
Area-Compilers
Bug
Concept-Diagnostic Clarity
The issues deals with the ease of understanding of errors and warnings.
help wanted
The issue is "up for grabs" - add a comment if you are interested in working on it
New Feature - Async Streams
Async Streams
New Language Feature - enhanced using
Using pattern and declaration
Milestone
Currently, we bind
x.Dispose()
and reject the result if it is an extension. But we should not even consider extensions, to avoid diagnostics about ambiguities.There is the same issue with binding
GetAsyncEnumerator
.The text was updated successfully, but these errors were encountered: