Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

Ah, thank you for pointing this out! I think I would suggest a change or two to your proposal, but I need to flesh them out first. Is it possible to leave comments on the bug site? BTW, why was it delegated to the bug report system in the first place? > On 28 Dec 2015, at 02:28, Erica Sadun

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

> method cascades I thought there was some sort of showstopper that ended further discussion for Swift 3 — but seems it wasn't the fault of the archive that I didn't find that reason ;-) I'll use the opportunity to talk about my major motivation to want cascades in Swift: Several years ago, I

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

> On 27 Dec 2015, at 21:55, Mosab Elagha wrote: > > Agreed, this seems like a great idea. Looks like it would also allow for a > lot of customization - for example out of one "template" object. > > Would the object have to already be initialized or could you initialize

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

Hi, That’s a great idea! Kind regards, Radek > On 27 Dec 2015, at 21:10, Taras Zakharko via swift-evolution > wrote: > > Quite often, one needs to perform a number of operations on a single object > (e.g. call up a bunch of configuration or action methods). This

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

-1 doesn't seem worth adding it is not a lot of trouble to type `obj.` at the start of every line. Also if an API is intended to be used like that its methods would return `self` and it would be used in a FLUENT style. Sent from my iPad > On 28 Dec 2015, at 9:00 AM, Erica Sadun via

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

The most common use-case for this is with Cocoa classes, which are not set up for fluent implementation. A preliminary proposal (which I am not updating since the matter was referred to the bug report system) is here: https://gist.github.com/erica/6794d48d917e2084d6ed Hopefully it explains the

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

Ah, thank you for pointing this out! I think I would suggest a change or two to your proposal, but I need to flesh them out first. Is it possible to leave comments on the bug site? BTW, why was it delegated to the bug report system in the first place? > On 28 Dec 2015, at 02:28, Erica Sadun

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

Same is true for the implicit self, and yet we’ve seen how people react to making self explicit. There are many places in contemporary Apple programming where this could be of great utility. For instance, I miss a lexical scope construction every time I work with Metal. > On 28 Dec 2015, at

Re: [swift-evolution] [Proposal] Lexical scope statement (with .. do)

I think it would be of great value to post both here and at the bug itself. Thanks! -- E, looking forward to it > On Dec 27, 2015, at 8:22 PM, Taras Zakharko > wrote: > > Ah, thank you for pointing this out! I think I would suggest a change or two > to your