<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 12, 2016, at 11:20, Jessy Catterwaul <<a href="mailto:mr.jessy@gmail.com" class="">mr.jessy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• "hTMLString" (a value) is nonsense to me; that's three words "h", "TML", and "String”.<br class=""></blockquote><br class=""><br class="">It was nonsense to me also. But I realized that we need to solve the problem of inconsistency, and forced myself to use it for a week. <br class=""><br class="">Now, it’s not nonsense, but instead, automatic and solves all relevant casing problems.</div></div></blockquote></div><br class=""><div class="">I see this as valuing internal consistency over consistency with the rest of the world, which seems like a Bad Idea. This violates "<a href="https://swift.org/documentation/api-design-guidelines/#use-terminology-well" class="">Use Terminology Well</a>" for me in the current draft API design guidelines. Identifiers are not sequences of characters; they are meant to be read.</div><div class=""><br class=""></div><div class="">Jordan</div></body></html>