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

[Shawn Erickson]

Note under the latest floating point and integer protocol proposals the
operators you outlined are basically overlays of the protocol functions
even abs is replaced with magnitude on a protocol. Sorry not in a situation
to link out to the proposals.

On Fri, Jul 1, 2016 at 7:51 AM Brad Hilton via swift-evolution <
swift-evolution at swift.org> wrote:

> > What is your evaluation of the proposal?
> I think it’s good to have this functionality in the standard library, but
> it seems a bit inconsistent with other Swift math operators which are
> declared as global functions such as abs, max, +, -, /, *, %, etc.
> > Is the problem being addressed significant enough to warrant a change to
> Swift?
> Yes, I believe that it would be useful to have these methods.
> > Does this proposal fit well with the feel and direction of Swift?
> As I mentioned before, it seems to be a departure from Swift’s other math
> operators. I think global functions such as floor(), ceil() and round()
> would be more consistent.
>
> > Hello Swift community,
> >
> > The review of "SE-0113: Add integral rounding functions to
> FloatingPoint" begins now and runs through July 5. The proposal is
> available here:
> >
> >
> https://github.com/apple/swift-evolution/blob/master/proposals/0113-rounding-functions-on-floatingpoint.md
> >
> > Reviews are an important part of the Swift evolution process. All
> reviews should be sent to the swift-evolution mailing list at
> >
> > https://lists.swift.org/mailman/listinfo/swift-evolution
> >
> > or, if you would like to keep your feedback private, directly to the
> review manager.
> >
> > What goes into a review?
> >
> > The goal of the review process is to improve the proposal under review
> through constructive criticism and contribute to the direction of Swift.
> When writing your review, here are some questions you might want to answer
> in your review:
> >
> > * What is your evaluation of the proposal?
> > * Is the problem being addressed significant enough to warrant a change
> to Swift?
> > * Does this proposal fit well with the feel and direction of Swift?
> > * If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
> > * How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
> >
> > More information about the Swift evolution process is available at
> >
> > https://github.com/apple/swift-evolution/blob/master/process.md
> >
> > Thank you,
> >
> > -Chris Lattner
> > Review Manager
> >
> >
> >
> >
> _______________________________________________
> 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/f3b90246/attachment.html>