<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That is correct, the proposed change only applies to the concrete slice types that are provided by the standard library.<div class=""><br class=""></div><div class="">Max<br class=""><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 23, 2016, at 5:13 PM, Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">[Proposal: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md%5D" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md</a>]</div><div class=""><br class=""></div><div class="">Hey, Max. For clarification, this isn’t adding anything to the <i class="">requirements</i> for slice types, correct? That is, the result type of 'subscript(_: Range)' has no additional requirements? (Why I ask: there would be plenty of implementations of slices that may not otherwise need a reference to the original collection.)</div><div class=""><br class=""></div><div class="">I’m vaguely uncomfortable with this because I feel like it’s violating some abstraction or allowing unsafe indexing, but of course that’s no more unsafe than with any other collection.</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 19, 2016, at 16:43, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">Hello Swift community,<br class=""><br class="">The review of "SE-0093: Adding a public base property to slices"<br class="">begins now and runs through May 23. The proposal is available here:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md</a><br class=""><br class="">Reviews are an important part of the Swift evolution process. All<br class="">reviews should be sent to the swift-evolution mailing list at<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""><br class="">or, if you would like to keep your feedback private, directly to the review manager.<br class=""><br class="">What goes into a review?<br class=""><br class="">The goal of the review process is to improve the proposal under review<br class="">through constructive criticism and contribute to the direction of<br class="">Swift. When writing your review, here are some questions you might<br class="">want to answer in your review:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>* What is your evaluation of the proposal?<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>* Is the problem being addressed significant enough to warrant a<br class=""> change to Swift?<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>* Does this proposal fit well with the feel and direction of<br class=""> Swift?<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>* If you have used other languages or libraries with a similar<br class=""> feature, how do you feel that this proposal compares to those?<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>* How much effort did you put into your review? A glance, a<br class=""> quick reading, or an in-depth study?<br class=""><br class="">More information about the Swift evolution process is available at<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre">        </span>https://github.com/apple/swift-evolution/blob/master/process.md<br class=""><br class="">Thank you,<br class=""><br class="">Dave Abrahams<br class="">Review Manager<br class=""><br class="">_______________________________________________<br class="">swift-evolution mailing list<br class="">swift-evolution@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></div></body></html>