<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 31 Mar 2017, at 12:33, Brent Royal-Gordon <<a href="mailto:brent@architechies.com" class="">brent@architechies.com</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=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 31, 2017, at 3:07 AM, Haravikk 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=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Is it actually in-use or just reserved? Not sure I've ever needed it in the debugger.</div></div></blockquote><div class=""><br class=""></div><div class="">Pop into the REPL for a minute:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>$ swift<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>Welcome to Apple Swift version 3.1 (swiftlang-802.0.41 clang-802.0.36). Type :help for assistance.<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span> 1> "hello"<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>$R0: String = "hello"<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span> 2> $R0<br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>$R1: String = "hello"<br class=""><br class=""></div><div class="">You may not have ever noticed it was there, but it was.</div></div></div></div></blockquote><div><br class=""></div><div>Is it always in the form of $R<n>? If it can't include periods then it doesn't seem like it would present a collision (just as overlap with $0, $1 etc. in closures does not).</div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class="">What about @? It has a certain appropriateness in how it reads for a path like: <font face="Monaco" class="">@Person.friend.lastName</font><br class=""></blockquote><blockquote type="cite" class=""><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></div></div></blockquote><div class=""><br class=""></div><div class="">We're already using @ for attributes; I don't think we want to overload its meaning.</div></div></div></blockquote><div><br class=""></div><div>Ack, no idea how I forgot about attributes considering I use them all the time. Hmm.</div><br class=""><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class="">Another alternative might be something like an unnamed compiler directive, for example: <font face="Monaco" class="">#(Person.friend.lastName)</font><br class=""></blockquote><blockquote type="cite" class=""><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">If you consider the statement to mean "expand this".</div><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""></span></div></blockquote><br class=""></div><div class="">The unnamed compiler directive seems like *really* valuable real estate, arguably much more so than unresolved-member-on-KeyPath-type is. I think it'd be foolish to assign it to anything before we have a macro system designed.</div></div></blockquote><br class=""></div><div>Perhaps, but how many other features might be making a bid for it? There's always the possibility of using a more "specialised" bracket for paths instead, like <font face="Monaco" class="">#{Person.friend.lastName}</font></div><div>Leaving regular parenthesis up for grabs for something else.</div></body></html>