-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
Forbid to have an extension method in the package owning the class #14354
Forbid to have an extension method in the package owning the class #14354
Conversation
It is currently possible to have a method that is an extension method that is in the same package as its class. This creates weird behaviors were some tools consider it an extension method and some other consider it not an extension method. To make thing more coherent I propose that we forbid to have this by classifying such methods under the unclassified protocol instead.
Apparently the warning is preventing the bootstrap to finish. Do you know what I should do so that it just log the problem and proceed? |
Checking the code of the compiler it seems that the right way would be to use a Notification or even a SystemNotification instead of a warning |
The build now passes and things are working correctly. In the non interactive environment things get logged. |
The last failure is fixed by this: pillar-markup/Microdown#658 But I need someone with merge rights :'( |
The requested changes were applied and the tests are now green |
It is currently possible to have a method that is an extension method that is in the same package as its class. This creates weird behaviors were some tools consider it an extension method and some other consider it not an extension method.
To make thing more coherent I propose that we forbid to have this by classifying such methods under the unclassified protocol instead.
Fixes ##14353