We're going to discuss the arbitrary self types v2 RFC. The author, @adetaylor, has laid out a compelling proposal for how the rules need to work if we want to support raw pointers, NonNull, etc. as receivers without making it a breaking change to later add methods to those types. The decision on the table is whether those rules are a price that we're willing to pay.
This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.
Summary
We're going to discuss the arbitrary self types v2 RFC. The author, @adetaylor, has laid out a compelling proposal for how the rules need to work if we want to support raw pointers,
NonNull, etc. as receivers without making it a breaking change to later add methods to those types. The decision on the table is whether those rules are a price that we're willing to pay.Background reading
NonNull, etc.About this issue
This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.