[swift-evolution-announce] Revision review: SE-104: Protocol-oriented integers

[Ben Cohen]

Hi Swift community,

Following feedback during the 4.0 preview, a handful of minor amendments have been suggested to SE-104: Protocol-oriented integers that the core team feels are important to include into 4.0 as they have an impact on source stability.

The review of this amendment begins now and runs through July 24th. 

The revised version of the proposal can be found here:
https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md

A summary of the amendments to the proposal under review can be found here:
https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md#whats-new-in-this-revision

This proposal does not reflect all of the feedback received on SE-104, but instead is a subset that are felt to be valuable _and_ easily achievable in 4.0 even at this fairly late stage of development. There are a few other items that the core team agree should be addressed, but will be deferred to a later version of Swift.

In order to get as much feedback as possible in the remaining time left, we intend to merge these changes on GitHub during the review, and will then fix in-place following the review if any significant new ideas that impact the proposal come up.

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 <https://lists.swift.org/mailman/listinfo/swift-evolution>

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:

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:
https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>


Thanks,

Ben Cohen

Review Manager


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution-announce/attachments/20170720/0dee3eb2/attachment.html>