Sounds great! It should be an easy one to get through,

> On 8 May 2017, at 08:35, Greg Spiers <gspi...@gmail.com> wrote:
> 
> 
> 
> On Mon, May 8, 2017 at 6:26 AM, David Hart via swift-evolution 
> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
> 
> 
> On 7 May 2017, at 20:12, Xiaodi Wu via swift-evolution 
> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
> 
>> Today these keywords have no meaning inside a protocol, so clearly it should 
>> be an error to use it in that context. I agree with Jordan that the error 
>> should be on the protocol.
>> 
>> It's entirely a different conversation whether the keyword should have 
>> meaning or not. If it should, it seems to me it should be limited to 
>> protocols that are limited to classes. But that's an additive feature we can 
>> discuss later.
>> 
>> The source-breaking bug fix that is more pressing today is removing 
>> meaningless keywords that can be misleading to users, because they have no 
>> effect but look like they should.
> 
> Exactly the trap I fell into when I found this issue.
>  
> 
> Yup, +1. Who wants to write a proposal?
> 
> I'd like to give it a try. I can write up the proposal to remove the keywords 
> in protocols and will post a draft here for further discussion.
>  
> 
>> On Sun, May 7, 2017 at 11:00 Goffredo Marocchi via swift-evolution 
>> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
>> It would be useful to have a longer discussion on this as... I think that 
>> weak has a place there and should be enforced as a protocol is the public 
>> facing interface/api for the types who decide to adopt it.
>> 
>> Sent from my iPhone
>> 
>> > On 7 May 2017, at 15:41, Adrian Zubarev via swift-evolution 
>> > <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote:
>> >
>> > browse
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution@swift.org <mailto:swift-evolution@swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution 
>> <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution@swift.org <mailto:swift-evolution@swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution 
>> <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org <mailto:swift-evolution@swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution 
> <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 
> 

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to