[swift-evolution] [Pitch] Computed properties as aliases

[Hooman Mehr]

Agreed. 

Actually, I was thinking about it while writing my response and wanted to go back and dig that thread to refresh my memory and bring it up. 

Thank you for taking care of that.

> On May 25, 2017, at 7:33 PM, Charles Srstka <cocoadev at charlessoft.com> wrote:
> 
>> On May 25, 2017, at 9:26 PM, Hooman Mehr via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> This is common when you are using façade design pattern. You use a façade to flatten and hide the internal composition of a composite object and present it as a single flat object. In some types of projects this comes up rather frequently. Both in client / UI programming and server side / business logic.
> 
> You know, what I would like to see instead of this would be a revival of the ‘automatic protocol forwarding’ concept that was pitched here very early on in the swift-evolution process:
> 
> https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151228/004737.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151228/004737.html>
> 
> This would be a much more flexible way to solve the same problem, and could also solve some problems that we used to use methods like forwardingTargetForSelector: for in Objective-C.
> 
> Charles
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170525/cfd8a0a3/attachment.html>