<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=""><div><blockquote type="cite" class=""><div class="">On 13 Dec 2015, at 15:32, David Hart 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 dir="auto" class=""><div class=""><blockquote type="cite" 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 class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">For the record I would also like it if the "globals must start with an uppercase letter" rule were enforced by the compiler (well, not in the playground, those aren't true globals). </span></font></blockquote><br 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=""></div><div class="">+1, in the same vein, global a should stand out :)</div></div></div></blockquote></div><br class=""><div class="">-1 from me.</div><div class=""><br class=""></div><div class="">I’d much prefer a way of name spacing free functions so that they don’t pollute global scope. That would help to reduce the potential ambiguity with implicit self too.</div></body></html>