Ha, I have that problem too of mistyping. I've often wondered if even just "bitPattern" might suffice, as the truncating or extending of it should not be particularly surprising. That said, I'm pretty convinced the current API needs time to settle before we reappraise.<br><div class="gmail_quote"><div dir="ltr">On Fri, May 26, 2017 at 01:57 Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
on Tue May 23 2017, Xiaodi Wu <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
<br>
> On Tue, May 23, 2017 at 11:47 PM, Guillaume Lessard via swift-evolution <<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
>><br>
>> > On May 23, 2017, at 19:55, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>> wrote:<br>
>> ><br>
>> > On Tue, May 23, 2017 at 5:27 PM, Guillaume Lessard via swift-evolution <<br>
>> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>> ><br>
>> > /// Truncating the fractional part of `source` is equivalent to rounding<br>
>> > /// toward zero.<br>
>> ><br>
>> > You are quite right; this is still there, and I didn't see it! Well,<br>
>> let's fix that.<br>
>><br>
>> Meanwhile, in the real world, truncation of a number or a series means<br>
>> reducing its precision. Of a floating point number, it’s removing the<br>
>> fractional part. Exactly the use you want to suppress. Why in the world do<br>
>> you insist that it must be redefined to be something else?<br>
><br>
> Let's be clear: this has nothing to do with what I want or like. This<br>
> decision was made previously, by other people. I am simply telling you what<br>
> it is and helping to ensure that it is consistently implemented. If you<br>
> were to go back into the archives, you'd see that I rather liked the<br>
> familiar names. But the time for debating that is over. Someone else's<br>
> arguments carried the day. We move on.<br>
<br>
FWIW, I for one would like to eventually reconsider things in this area,<br>
having used the new APIs. <a href="https://bugs.swift.org/browse/SR-4689" rel="noreferrer" target="_blank">https://bugs.swift.org/browse/SR-4689</a> is relevant.<br>
<br>
--<br>
-Dave<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>