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

[Kenny Leung]

I’m all for this, but couldn’t it be done without the “with”? It doesn’t seem to make the code read any easier.

This

    myObject {
        this = that
        here = there
    }

could unambiguously indicate that you want method cascading.

Or even

    myObject.{
        this = that
        here = there
    }

which has a relationship to the current method invocation syntax.

-Kenny


> On Dec 9, 2015, at 9:47 AM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Here you go:  https://bugs.swift.org/browse/SR-160
> 
> Let me also point you to this:  https://gist.github.com/erica/6794d48d917e2084d6ed because
> 
> * It is pretty
> * I put a lot of effort into it, following the "social" request in the current process document, etc
> * I want to publicly shower props on Sean Heber, who showed great patience, insight, and kindness helping out on this
> 
> I'd appreciate any advice you could share on determining which tool to use when you have a Swift enhancement idea
> 
> -- E
> 
> 
>> On Dec 8, 2015, at 10:16 PM, Chris Lattner <clattner at apple.com> wrote:
>> 
>> 
>>> On Dec 7, 2015, at 4:46 PM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
>>> 
>>> Noted. Since an updated proposal is all but ready, could we please have a Swift 4 proposal daycare folder to stick it in, so it doesn't get lost or forgotten?
>> 
>> Personally, I’d rather use bugs.swift.org for feature requests like this.  It is lighter weight, allows commenting, etc.
>> 
>> -Chris
>> 
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution