[swift-evolution] [Review] SE-0093: Adding a public base property to slices

[Max Moiseev]

That is correct, the proposed change only applies to the concrete slice types that are provided by the standard library.

Max


> On May 23, 2016, at 5:13 PM, Jordan Rose <jordan_rose at apple.com> wrote:
> 
> [Proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md <https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md%5D>]
> 
> Hey, Max. For clarification, this isn’t adding anything to the requirements 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.)
> 
> 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.
> 
> Jordan
> 
> 
>> On May 19, 2016, at 16:43, Dave Abrahams via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> 
>> Hello Swift community,
>> 
>> The review of "SE-0093: Adding a public base property to slices"
>> begins now and runs through May 23. The proposal is available here:
>> 
>> 	https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.md <https://github.com/apple/swift-evolution/blob/master/proposals/0093-slice-base.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.
>> 
>> What goes into a review?
>> 
>> The goal of the review process is to improve the proposal under review
>> through constructive criticism and contribute to 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,
>> 
>> Dave Abrahams
>> Review Manager
>> 
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160523/12dcf180/attachment.html>