[swift-evolution] [swift-evolution-announce] [Review] SE-0113: Add integral rounding functions to FloatingPoint

[Xiaodi Wu]

Given that 2 * pi is always as precise as pi itself, I really can't
understand the clamor for such a constant in the stdlib. It can be defined
both correctly and trivially by anyone who wants it.
On Fri, Jul 1, 2016 at 12:21 Erica Sadun via swift-evolution <
swift-evolution at swift.org> wrote:

>
> On Jul 1, 2016, at 11:13 AM, Stephen Canon via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> On Jul 1, 2016, at 1:11 PM, Jordan Rose via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>
> [Proposal:
> https://github.com/apple/swift-evolution/blob/master/proposals/0113-rounding-functions-on-floatingpoint.md
>  ]
>
> Just wondering, why no 'awayFromZero' case?
>
>
> It’s not defined or required by IEEE 754.  The others are.  I wouldn’t be
> opposed to adding some other rounding modes, but the IEEE 754 set is as
> good as any as a starting point.
>
>
> I'm  hearing a lot of "Wouldn't it be nice if"s, for items falling outside
> IEEE 754. Could we have a native Math module that offered such niceties
> under a separate umbrella proposal? Would it be too cluttery to allow
> things like Double.tau, etc via a Math.Double extension or however that
> might work?
>
> -- E, who abides by Canon law
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160701/73698bbd/attachment.html>