Hello Swift community,

Context: One more small refinement proposal for Swift 4 strings.  We are 
specifically not opening the floodgates for new proposals yet, this is this 
simply one potential small-scope refinement to an existing Swift 4 feature.


The review of "Substring performance affordances" begins now and runs through 
July 21, 2017. The proposal is available here:
https://github.com/apple/swift-evolution/blob/master/proposals/0183-substring-affordances.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. 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


Thank you,

Chris Lattner
Review Manager


_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to