<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 class="">Hi Howard, thanks for the feedback.</div><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 6:05 PM, Howard Lovatt <<a href="mailto:howard.lovatt@gmail.com" class="">howard.lovatt@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">+1 great addition.<div class=""><br class=""></div><div class="">Would suggest the naming could be more consistent, in particular:</div><div class=""><ol class=""><li class="">Anything returning Self could be named xxxed. In the current proposal this naming convention is sometimes used, e.g. divided, and sometimes not, e.g. subtracting. Suggest all unified with the xxxed convention.</li></ol></div></div></div></blockquote>The names in the Arithmetic protocol are Dave A’s creation, but I think they’re a reasonable compromise given the constraints placed on us. While consistency would be nice, I think that clarity at use site is more important, under the rationale that code is read more often than written. Also, keep in mind that in practice, “everyone” will use the operators for arithmetic. Dave may have more to say on the subject.</div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><ol class="" start="2"><li class="">Anything returning Bool could be named isXxx. In some cases this is used, e.g. isUnordered, but not others, e.g. totalOrder.</li></ol></div></div></div></blockquote>That’s a reasonable point. isTotallyOrdered(with: ) is simple, but I’m not sure how I would handle totalOrderMagnitude( ) under this scheme. Thoughts?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">– Steve</div></body></html>