<div dir="ltr">+1 for both. I find that I use $0 enough in closures that I have no problem remembering what it does, and being able to use it for setters would save me a bunch of typing.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 2:24 PM, Jessy Catterwaul via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">If functions start using shorthand argument names, I would probably feel more comfortable with it. Is that being discussed?<div><div class="h5"><div><br><div><blockquote type="cite"><div>On Feb 3, 2016, at 5:22 PM, T.J. Usiyan <<a href="mailto:griotspeak@gmail.com" target="_blank">griotspeak@gmail.com</a>> wrote:</div><br><div><div dir="ltr">+1 for both. I don't think that I would prefer the $0 syntax in most cases but I would appreciate making the syntax more consistent.<div><br></div><div>TJ</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 5:08 PM, Jessy Catterwaul via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>+1 on implicit return</div><div>-1 on $0; I like newValue more than it.</div><div><br></div><div>I also think the return <u>type</u> should be implicit.</div><br><div><blockquote type="cite"><div><div><div>On Feb 3, 2016, at 5:00 PM, Chris Liscio via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br></div></div><div><div><div><div style="word-wrap:break-word"><div>Why can’t we use shorthand argument names and implicit returns when specifying the get and set blocks in a computed property? I.e., Why must we refer to newValue in the implementation of set, and not $0 like we do in closures? Also, why do we need ‘return’?</div><div><br></div><div>Once you get used to the shorthand, you kinda want to use it all over…</div><div><br></div><div>This question came up recently when I was writing a façade for another class, and would have liked to written something like the following:</div><div><br></div><div><font face="Menlo">class Façade {</font></div><div><font face="Menlo"> private var _wrapped: Something</font></div><div><font face="Menlo"><br></font></div><div><font face="Menlo"> var wrappedProperty: Int {</font></div><div><font face="Menlo"> get { _wrapped.property }</font></div><div><font face="Menlo"> set { _wrapped.property = $0 }</font></div><div><font face="Menlo"> }</font></div><div><font face="Menlo"><br></font></div><div><font face="Menlo"> var multipliedProperty: Int { _wrapped.property * 42 }</font></div><div><font face="Menlo">}</font></div><div><br></div>I apologize if this has already been discussed/requested before. I searched the archives and didn’t turn up anything that referred to this specifically.<div><br></div><div>Thanks!</div><div><br></div><div><div>Chris Liscio</div><div><a href="http://supermegaultragroovy.com/" target="_blank">http://supermegaultragroovy.com</a></div><div>Learn _your_ music with Capo: <a href="http://capoapp.com/" target="_blank">http://capoapp.com</a></div></div><div><br></div></div></div></div>_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>