Alternatives to BinaryCompatOnlyAttribute #7717
Replies: 1 comment 2 replies
-
These have already been suggested on the original issue, we don't need a separate discussion to fracture the conversation and make it harder to follow. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Context
Since the main motivation for
BinaryCompatOnlyAttribute
is to resolve overload resolution problems, I propose this be resolved by changingObsoleteAttribute
instead.Idea 1: Make Obsolescence Affect Overload Resolution
We define an "obsolete context" where a containing type or member is obsolete. In this context, overload resolution is treated the same as it is today.
Outside of an obsolete context, obsolete members are treated as a last resort for resolution, perhaps even after extension members with the same signature.
Idea 2: Add a Boolean Property to ObsoleteAttribute
Beta Was this translation helpful? Give feedback.
All reactions