<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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="">On Feb 2, 2016, at 11:12 AM, Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hmm...the rationale that Joe provided makes a lot of sense.<div class=""><br class=""></div><div class="">One question - is the explicit closure syntax amenable to multiple levels of currying? In particular, what are the scoping rules for the placeholders $<i class="">n </i>- are they limited to the immediate closure within which they appear, or can they be used within further-nested closures?</div></div></div></blockquote><br class=""></div><div>Currently, they're always scoped to the immediate closure, so you need to use explicit named parameters if you want to nest closures.</div><div><br class=""></div><div>-Joe</div><br class=""></body></html>