<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class=""> cars.map{.make}</div></div></div></div></div></blockquote><br class=""></div><div class="">This last alternative looks a lot like a special (single expression) case of the Method Cascading proposal <<a href="https://bugs.swift.org/browse/SR-160" class="">https://bugs.swift.org/browse/SR-160</a>>. If you want to go forward with this shorthand, I’d suggest adding it to method cascading as a rule: Invoking a closure with a single anonymous argument also implicitly begins a cascade with $0 as the default receiver.</div></div></div></blockquote><br class=""></div><div>Thanks for bringing this up! It is not a special case of that specific proposal but it is a special case of a variation of the proposal that was discussed. Seeing it applied in this context is really interesting. </div><div><br class=""></div><div>Joe Groff noted syntactic ambiguity caused by omitting $0. Unless that potential ambiguity could be resolved in some way this wouldn’t actually work. It does work if you include $0:</div><div><br class=""></div><div>cars.map{$0.make}</div><div><br class=""></div></body></html>