<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 Feb 3, 2016, at 5:31 PM, Erica Sadun <<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</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=""><div class=""><blockquote type="cite" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On Feb 3, 2016, at 4:39 PM, Chris Lattner <<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class=""><div class="">Proposal Link: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md</a></div><div class=""><br class=""></div>The review of SE-0028 "<b class="">Modernizing Swift's Debugging Identifiers</b>" ran from January 29… February 2, 2016. The proposal has been *<b class="">accepted*</b>, with modifications:<div class=""><br class=""></div><div class="">* The core team agrees that we should rename all of the existing __FILE__, __LINE__, __COLUMN__, __FUNCTION__, and __DSO_HANDLE__ symbols to lowercase equivalents in the # namespace: #file, #line, #column, #function, #dsohandle. This includes keeping __FUNCTION__, </div></div></div></blockquote><div class=""><br class=""></div></span><div class="">To clarify, I meant keeping the behavior of __FUNCTION__, but renaming it to #function.</div></div></div></blockquote></div></div></div></blockquote><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span style="font-family: Palatino-Roman;" class="">* The core team requests that #symbol be split out into a separate proposal, because it needs more detailed design work, and is an additive feature. For example, it might be appealing to provide a "#mangledName” expression that provides the current symbol as a mangled name: when fed into a demangler, a more structured form of the current symbol would be available.</span></blockquote></blockquote><br class=""></div><div class="">A few q's:</div><div class=""><span style="font-family: Palatino-Roman;" class=""><br class=""></span></div><div class=""><span style="font-family: Palatino-Roman;" class="">* </span><font face="Menlo" class="">#mangledname</font><span style="font-family: Palatino-Roman;" class="">, I presume? To retain lowercase? </span></div></div></div></blockquote><div><br class=""></div>Yes, that would make sense. However, the demangler API’s aren’t currently very awesome for Swift, so this may be a theoretical goal. We should discuss whether this idea even makes sense.</div><div><br class=""><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=""><span style="font-family: Palatino-Roman;" class="">* Do you want #symbol (e.g. Swift.Dictionary.Foo(_: Int, y: CustomType)) pushed now or saved for post 3.0? (Although SE-0021 is in 2.2?)</span></div></div></div></blockquote><div><br class=""></div><div>It’s fine to discuss it now. Things that need to be figured out are things like: how specific to make this? In a getter, should it say the getter, or just the property? In a closure within a getter, should it somehow indicate the closure, or just the getter? etc.</div><div><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=""><span style="font-family: Palatino-Roman;" class="">* Will #context/#releasecontext/#debugcontext be split out to a separate proposal or dropped entirely?</span></div></div></div></blockquote><br class=""></div><div>I think they’d have to be separately motivated by a problem being solved, and being separate is good.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>