<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="">Same here<br class=""><div><blockquote type="cite" class=""><div class="">On Jan 29, 2016, at 11:49, Adrian Kashivskyy 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=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">What is your evaluation of the proposal?</blockquote><div class=""><br class=""></div>I'm +1 on this. In my opinion it aligns well with other static compiler directives such as `#selector`, `#available`, #if`.<br class=""><div class=""><br class="webkit-block-placeholder"></div><div class=""><blockquote type="cite" class="">Is the problem being addressed significant enough to warrant a change to Swift?</blockquote><br class=""></div><div class="">Yes, those identifiers are used often when debugging (especially logging).</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">Does this proposal fit well with the feel and direction of Swift?</blockquote><br class=""></div><div class="">Definetely yes. It removes yet another C artifact which cannot be justified in any way except of familiarity. Also, `#`-prefixed keywords fit well with other compiler expressions (this argument was mentioned in the proposal itself).</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</blockquote><br class=""></div><div class="">Obviously, in C family languages. As C family libraries and frameworks tend to name their basic constants using `__SCREAMING_SNAKE_CASE__` format so that `__FILE__` fits well among them, it is not the case in Swift.</div><div class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><font color="#929292" class=""><br class="Apple-interchange-newline">Pozdrawiam – Regards,</font></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><font color="#929292" class="">Adrian Kashivskyy</font></div></div></div></div></blockquote></div><br class=""></body></html>