Judging from doug's email, i was thinking that the format of the ideal proposal should be somewhere in between what Austin did and what i played with so far. It is still a small exercise in trying to show how things do not have to be so complicated, but 3.0 is still very much today's focus.
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160530/020159.html > On Jun 15, 2016, at 5:51 PM, Adrian Zubarev via swift-evolution > <swift-evolution@swift.org> wrote: > > +1 > > -- > Adrian Zubarev > Sent with Airmail > Am 15. Juni 2016 um 16:56:44, Austin Zheng (austinzh...@gmail.com) schrieb: > >> >>> On Jun 15, 2016, at 3:35 AM, L. Mihalkovic via swift-evolution >>> <swift-evolution@swift.org> wrote: >>> >>> >>> >>> On Jun 15, 2016, at 8:24 AM, Adrian Zubarev via swift-evolution >>> <swift-evolution@swift.org> wrote: >>> >>>> I guess you don’t understand that a so called proposal should have enough >>>> details to explain the proposed behavior to someone who is not the author >>>> of the proposal. You’re offering is fine but a few unexplained lines of >>>> your gist wouldn’t make through a proposal review at all. >>>> >>> I'm sure you have no doubt understood that it is NOT a formal proposal yet, >>> but more a attempt at showing that the current ones are far more >>> complicated than they ought to be. >> >> If you think a proposal comprised of a handful of examples is sufficient to >> explain the feature, please do prepare and submit one. If the core team >> accepts it for review, you will have saved everyone a lot of time. >> >> Best, >> Austin > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
