[swift-evolution] Ownership on protocol property requirements

Xiaodi Wu xiaodi.wu at gmail.com
Mon May 8 04:15:04 CDT 2017


On Mon, May 8, 2017 at 2:52 AM, Goffredo Marocchi <panajev at gmail.com> wrote:

>
>
> Sent from my iPhone
>
> On 8 May 2017, at 08:44, Xiaodi Wu <xiaodi.wu at gmail.com> wrote:
>
> On Mon, May 8, 2017 at 2:40 AM, Goffredo Marocchi via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>> I can understand that, I am just wary of "let's do a partially
>> detrimental change
>>
>
> The key here is that there is no detriment to this change. There's no
> functionality that's being removed, only misleading syntax.
>
>
> Why is it misleading? Because it is not enforced,
>

Right, and there is clearly no chance of it being enforced in Swift 4, so
it is either going to be unenforced and misleading, or not permitted and
not misleading.


> but protocol extension default methods being shadowable but not
> overridable and presenting no warning is a very similar issue...
>

That is totally another topic.


> if the answer is the same there (at least for classes), I am more than
> happy to get both changes ;).
>
>
>
>> no... we will... we will make it proper someday" kind of changes as they
>> seldom work out. Argument labels for stored closures and callbacks are
>> still lost for example :/...
>>
>
> That's a totally different issue. Someone needs to write the proposal and
> implementation for that.
>
>
> Would you and some other be willing to help me (Erica?)? A lot to ask, but
> it would be important although a bit beyond the scope for "dweller's first
> proposal" especially the implementation and grammar side. I do not think it
> has a iota of chance for it to get integrate in time though :/.
>

It clearly doesn't have any chance of implementation for Swift 4. The
proposal itself doesn't need much as it's already spelled out; it's
entirely the implementation that needs work, for which I have neither the
time nor the expertise. Since it is an additive change, though, there
really is no rush as it can be done at any time. There are just so many
other priorities.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170508/885d116f/attachment.html>


More information about the swift-evolution mailing list