[swift-evolution] Straw Poll. Re: Method cascading (was Re: Request for Discussion: Setup closures)

Erica Sadun erica at ericasadun.com
Mon Dec 7 09:41:29 CST 2015

Following this weekend's discussions, I'm running a quick poll. It's short. 

FEAGTURE WRITE-UP:  https://gist.github.com/erica/eb32feb22ba99629285a
POLL HERE:  https://www.surveymonkey.com/r/KFYD5RT

I want to gauge interest in method cascading so I don't push a proposal without reasonably broad support.

Thank you -- Erica

> On Dec 7, 2015, at 12:08 AM, Tino Heth via swift-evolution <swift-evolution at swift.org> wrote:
> Nice to see that most points from my wishlist 
> are already discussed here ;-)
> I didn't even know this feature got a name, but it
> would be great for working with graphic contexts
> and some orher tasks.
> But I would prefer another approach over a new keyword:
> context.{
> moveTo(x: 23, y: 42)
> lineTo(x: 0, y: 0)
> }
> is quite intuitive to me, and I can't see any downsides so far
> (first thought was just braces without the dot, but that
> could clash when you want to use the syntax with the
> return value of a function, which could have a trailing closure).
> Something similiar could be archieved by dropping
> void as default return value in favour of self...
> Von meinem iPhone gesendet
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list