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

[Stephen Christopher]

Partial initializers + forwarding is in line with what I’ve been imagining
as well. I look forward to seeing this fleshed out more.

Step Christopher
Big Nerd Ranch, LLC
schristopher at bignerdranch.com


On Sun, Jan 10, 2016 at 3:28 PM, Matthew Johnson via swift-evolution <
swift-evolution at swift.org> wrote:

>
>
> Sent from my iPhone
>
> On Jan 10, 2016, at 11:20 AM, Thorsten Seitz <tseitz42 at icloud.com> wrote:
>
> Unfortunately I’m in the wrong time zone: 8 pm CST means 3 am of the next
> day here in Europe and I’d rather not get up in the middle of the night :-)
> Bad luck that today you have dads duty but that’s life and there are more
> important things than Swift evolution. I mean that sincerely, so don’t
> worry about it.
>
> I hadn’t expected a full draft of your vision, I just had hoped for one or
> two lines to get an idea of your vision, no need to finish the draft for
> that.
>
>
> Hi Thorsten.  I have time for a quick teaser.  It may or may not mean much
> without the details so watch for those tonight / in the morning.
>
> The general approach I plan to outline uses partial initializers, concise
> syntax for declaring memberwise partial initializers, a general parameter
> forwarding mechanism, and sugar for directly forwarding to a partial
> initializer.  Obviously this is more than just one proposal.
>
> There is a very clear and straightforward migration path from the current
> proposal to the general solution if the necessary features are accepted.
>
> More on this later tonight.
>
> Matthew
>
> But I understand that now is a bad moment to send me something, so no
> worries. Have a nice day with your son!
>
> -Thorsten
>
> Am 10.01.2016 um 16:35 schrieb Matthew Johnson <matthew at anandabits.com>:
>
> On Jan 10, 2016, at 9:26 AM, Thorsten Seitz <tseitz42 at icloud.com> wrote:
>
> Hi Matthew,
>
> Am 10.01.2016 um 15:03 schrieb Matthew Johnson <matthew at anandabits.com>:
>
> On Jan 10, 2016, at 4:08 AM, Thorsten Seitz via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> Am 10.01.2016 um 10:37 schrieb Brent Royal-Gordon <brent at architechies.com
> >:
>
> But it seems to me that what we're going to end up with is that, instead
> of having this:
>
>   public init(members...: Members) {
>       self.members = members
>   }
>
> We'll have something more like:
>
>   public init(members...: Members.Public.Initializable) {
>       self.members.public.initializable = members
>   }
>
>
> Yes, that’s just what I’m trying to find out: I do like the Members-based
> idea but wanted to get a clearer understanding how it might *really* unfold
> before casting my vote for the current proposal.
>
>
> I will be sharing my vision for a long-term direction later today or
> tomorrow.  It allows us to accept this proposal as a step forward while
> still having a long-term path that relies on more general features, with a
> clean migration path when the more general features are ready.
>
>
> That sounds great! Would you mind sharing a sketch of your idea today just
> to get a rough feeling before the review ends?
>
>
> I would like to.  I need a little bit more time to finish the drafts
> before sharing.  I have dad duty on Sundays so I won't be able to do that
> until until my son goes to bed.  I am hoping to be ready to share them by
> about 8 or 9 CST tonight.  That still leaves a few hours while the review
> is open.
>
> Matthew
>
>
>
> _______________________________________________
> 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/20160110/b5aa36f7/attachment.html>