[swift-evolution] Should we rename "class" when referring to protocol conformance?
atrick at apple.com
Tue May 10 00:53:17 CDT 2016
> On May 9, 2016, at 4:07 PM, Matthew Johnson <matthew at anandabits.com> wrote:
> I’m also interested in your feedback on whether a proposal around indirect is something worth pursuing right now or whether that is something that should wait until after Swift 3.
I’m not prepared to champion this for Swift 3, I think there are enough other important proposals on the table, and this is an area that requires careful design. If I did have to pick features that we touched on in this thread from most to least important I would say:
1. Indirect structs
2. Mutability of reference/class types
3. Automation or annotations for CoW types.
4. Annotations that constrain function side effects.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution