Accidentally hit send! Sorry everyone. Here's what I was originally looking for: a diff between the old and new revisions of the proposal: https://github.com/apple/swift-evolution/commit/0d163c941261b6d16d1adfdc3212e8d3a15a3a73#diff-6034851c9ada9528665f7555a93537a8 <https://github.com/apple/swift-evolution/commit/0d163c941261b6d16d1adfdc3212e8d3a15a3a73#diff-6034851c9ada9528665f7555a93537a8>
Jordan > On Jun 26, 2017, at 10:47, Jordan Rose <jordan_r...@apple.com> wrote: > > > > >> On Jun 22, 2017, at 17:10, Ted Kremenek <kreme...@apple.com >> <mailto:kreme...@apple.com>> wrote: >> >> Proposal Link: >> https://github.com/apple/swift-evolution/blob/master/proposals/0180-string-index-overhaul.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0180-string-index-overhaul.md> >> >> The review of “SE-0180 - String Index Overhaul” ran from June 4…8, 2017. >> >> Feedback on the proposal and further discussion in the Core Team has >> resulted in a slightly revised proposal. A revised review of that proposal >> will run from now until June 28. >> >> The revised proposal focuses on feedback concerning cases where indices fall >> between Unicode scalar boundaries in views having distinct encodings. >> Please see the revised review (link above) for the specific technical >> revisions. >> >> Thanks to everyone who participated in providing feedback for the review, >> and please take a look at the revised proposal! >> >> - Ted >> Review Manager >> >> — REVISED REVIEW — >> >> When replying, please try to keep the proposal link at the top of the >> message: >> >> Proposal link: >> >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0180-string-index-overhaul.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0180-string-index-overhaul.md> >> 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: >> >> https://github.com/apple/swift-evolution/blob/master/process.md >> <https://github.com/apple/swift-evolution/blob/master/process.md>_______________________________________________ >> swift-evolution-announce mailing list >> swift-evolution-annou...@swift.org >> <mailto:swift-evolution-annou...@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution-announce >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
