> * What is your evaluation of the proposal? No mistake: this is a pretty ugly solution to the problem. However, it *is* a problem that badly needs solving, and all the other solutions (like "always use the float logic and let the optimizer fix it up into integer logic") are far worse. So I believe this proposal should be accepted.
> * Is the problem being addressed significant enough to warrant a change > to Swift? Yes. Striding simply doesn't work properly on floating-point types right now. That needs to be fixed. > * Does this proposal fit well with the feel and direction of Swift? Yes. > * If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? Most languages I've used just let you write shitty floating-point code. It's nice to see Swift helping you write good floating-point code. > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Quick reading and some private experiments. -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
