<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="" applecontenteditable="true"><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 22, 2017, at 10:48 AM, David Sweeris 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=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Eh, maybe… At least in Xcode, autocomplete works for free functions. I was just thinking about how people who already know about “signum" would expect it to work. Like if a mathematician sits down to write something in Swift, are they more likely to try “signum(x)” or “x.signum” first?</span></div></blockquote></div><br class=""><div class="">Honestly, as a mathematician I think either one is fine.</div><div class=""><br class=""></div><div class="">We like free functions in mathematics. x.signum is (slightly?) Swiftier. Six of one, half dozen of the other, either one will be completely satisfactory.</div><div class=""><br class=""></div><div class="">– Steve</div></body></html>