[swift-evolution] [Re-Review] SE-0104: Protocol-oriented integers
ben_cohen at apple.com
Thu Feb 23 20:05:04 CST 2017
The core team met and reviewed the discussion of this proposal so far, and had the following mid-review feedback to relay back to the list:
Regarding the “Number” protocol: it was felt this is likely to cause confusion with NSNumber, given the NS-prefix-dropping versions of other Foundation types indicate a value-typed concrete type equivalent, which this won’t be. The recommendation is to use “Numeric" instead.
Regarding the question of the trailing argument to distinguish overflow-checking vs expanding versions of multiplied: rather than add an enum or use the void trick in order to do this via arguments, it is better to just distinguish the two functions via different base names.
Regarding restoring the BitwiseOperations protocol – the team feels that the bitset use case can be modeled with SetAlgebra rather than retaining a protocol with only bitwise operators.
popcount – although this is a term of art, in general it’s best to avoid abbreviations, so the suggestion is to rename it populationCount, which also helps settle whether the “c” should be capitalized and confusion over the other meaning of “pop".
> On Feb 17, 2017, at 5:45 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> The re-review of SE-0104 "Protocol-oriented integers" begins now and runs through February 25, 2017. This proposal was accepted for Swift 3, but was not implemented in time for the release. The revised proposal is available here:
> https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md <https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:
> Proposal link:
> Reply text
> Other replies
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine 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
> Thank you,
> -Joe Groff
> Review Manager
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution