> On Jul 14, 2016, at 11:27 PM, Brent Royal-Gordon via swift-evolution 
> <[email protected]> wrote:
> 
>> On Jul 14, 2016, at 2:39 PM, Chris Lattner <[email protected]> wrote:
>> 
>> asks the community for an in-depth discussion of the secondary points of the 
>> proposal: does it make sense to require every member to be marked as 
>> “overridable” in order to be overridden by an open subclass outside of the 
>> current module?
> 
> To be clear: You want this discussion to happen in the next review thread, 
> rather than in this thread?

Yep, I’ll kick off another review period as soon as the proposal is revised 
(hopefully today).

-Chris
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to