+1. This is well thought out and an important evolution of string. > On Apr 5, 2017, at 11:39 AM, John McCall via swift-evolution > <[email protected]> wrote: > > Hello, Swift community! > > The review of "SE-163: String Revision: Collection Conformance, C Interop, > Transcoding" begins now and runs through next Tuesday, April 11th. The > proposal is available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0163-string-revision-1.md>
> 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? +1 > • Is the problem being addressed significant enough to warrant a change > to Swift? Yes > • 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? Swift is ahead of most other languages in sweeping unicode support, and this refines swift’s position. > • How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Multiple readings, but not in-depth study.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
