<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="">On Mar 12, 2016, at 2:17 AM, Антон Жилин via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">#sourceLocation(file: "foo", line: 42) &nbsp; &nbsp;// Set logical position.</div><div class="">#sourceLocation() &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;// Reset logical position.</div><div class=""><br class=""></div><div class="">I fully support renaming of the first directive, but have a tiny concern about the second one.</div><div class="">Does sourceLocation name reflect its purpose? Maybe resetSourceLocation or something like that?</div></div></div></blockquote><br class=""></div><div>Perhaps</div><div>&nbsp; &nbsp; #sourceLocation(reset)</div><div><br class=""></div><div>which provides space for other potential future constructs</div><div>&nbsp; &nbsp; #sourceLocation(push)</div>&nbsp; &nbsp; #sourceLocation(file:"foo", line: 42)<div class="">&nbsp; &nbsp; …<br class=""><div class="">&nbsp; &nbsp; #sourceLocation(pop)</div><div class=""><br class=""></div></div><div class=""><br class=""></div><div class="">--&nbsp;</div><div class="">Greg Parker &nbsp; &nbsp; <a href="mailto:gparker@apple.com" class="">gparker@apple.com</a>&nbsp; &nbsp; &nbsp;Runtime Wrangler</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>