[swift-evolution] [Review] SE-0018 Flexible Memberwise Initialization

[Tal Atlas]

It’s a common use case to have a private stored object that’s set
externally via the initializer, I think having a solution that doesn’t
support that would be a big mistake.

On Fri, Jan 8, 2016 at 11:08 AM Tal Atlas <me at tal.by> wrote:

> My biggest problem is what does member wise even mean the averts person.
> And a naked ... Is a spread operator in most languages and doesn't mean
> anything inherently.
>
> I worry about arguing about the specifics because this is way better than
> the current state but I very much think the details of this proposal are
> confusing to the average developer and is more restrictive to any future
> use of the spread operator.
>
> On Thu, Jan 7, 2016 at 8:25 PM Brent Royal-Gordon via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>> > We will probably have warning flags eventually.
>>
>> I don't know what makes you think so. The language has so far carefully
>> avoided this, and we've heard some pretty strong statements from the core
>> team against the idea of compiler flags and incompatible dialects.
>>
>> --
>> Brent Royal-Gordon
>> Architechies
>>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160108/e30f1940/attachment.html>