<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 Jul 2, 2016, at 2:39 PM, Riley Testut 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=""><div class=""><blockquote type="cite" class=""><span class="" style="float: none; display: inline !important;">When naming, we need to learn to stop treating the comfortable ring of</span><br class=""><span class="" style="float: none; display: inline !important;">familiar word patterns as an arbiter of success.</span></blockquote><br class=""></div><div class="">I’m not sure I agree with this statement. I would argue we should most <i class="">certainly </i>aim to keep a consistent feel across our naming conventions...</div><div class="">Following that, “ExpressibleAsIntegerLiteral” feels extremely un-swiftyPI Guidelines, the fact that it’s the only protocol with the adjective at the beginning and not the end is a giant red flag to me (unless I’m missing some)....</div></div></div></blockquote><br class=""></div><div>Change it to "Syntax.ExpressibleByIntegerLiteral" and I'd be onboard but</div><div>I don't think it would pass the DaveTest despite it being only 2 characters longer.[1]</div><div><br class=""></div><div>-- E [2]</div><div>[1] I'd probably even buy into "From" instead of "By".</div><div>[2] I keep *promising* myself to stop adding to this conversation and pull an Elsa.</div><div>My success rate at keeping this promise is, as yet, suboptimal.</div><div><br class=""></div><br class=""></body></html>