<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=""><blockquote type="cite" class="">I understand why the alternative of changing the generic type parameter list symbols was rejected, to be consistent with other C based languages, but I don't understand why the following was rejected:</blockquote><div><blockquote type="cite" class=""><div dir="auto" class=""><div class=""><br class=""></div><div class=""><ul style="box-sizing: border-box; padding-left: 2em; margin-top: 0px; margin-bottom: 16px;" class=""><li style="box-sizing: border-box;" class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">making the <code style="box-sizing: border-box; padding: 0.2em 0px; margin: 0px; border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px;" class="">UppercaseTypes</code>, <code style="box-sizing: border-box; padding: 0.2em 0px; margin: 0px; border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px;" class="">lowercaseValues</code> convention a syntactic requirement, as is done in ML and Haskell.</span></li></ul><div class="">I see that as a good viable alternative.</div></div></div></blockquote></div><br class="">
+1, enforcing the initial character case of type and value identifiers would clear up the language IMO.<div class=""><br class=""></div><div class="">It would also mean we'd need to bridge all C APIs in correct case.</div><div class=""><br class=""></div><div class="">Also, in general +1 to getting rid of `.self`.</div><div class=""><br class=""></div><div class="">— Pyry</div></body></html>