[swift-evolution] [swift-evolution-announce] [Review] SE-0069: Mutability and Foundation Value Types
phausler at apple.com
Thu Apr 28 00:29:54 CDT 2016
I haven't tried to directly replace them yet but I would imagine that in order to replicate behavior some of the reference types will still be needed. That being said, other classes may no longer have any real value (not fully intended to be a pun) since types like NSDate are just simple wrappers around a simple value type. There will be a few parts: like coding or property lists that will still need to internally require a reference type to manipulate in CF code.
The boxing types will be simpler than the overlay for Objective-C since the corelibs version are all Swift classes at their base.
In short I think it would be best to just add and not remove things for now from swift-corelibs-foundation when modifications are made to bring these in sync.
Sent from my iPhone
> On Apr 25, 2016, at 8:35 PM, David Waite via swift-evolution <swift-evolution at swift.org> wrote:
> - The sentences "These new struct types will be implemented in the Swift overlay. Immutable/mutable pairs (e.g. Data and MutableData) will become one mutable struct type” are a duplicate and may be a copy/paste error.
> - I am unsure when a new struct type contains a mutable or immutable boxed object.
> - Is there a goal to eventually replace/remove the NS* versions completely within corelibs-foundation?
>> On Apr 25, 2016, at 4:21 PM, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
>> Enormous +1. This is a no-brainier IMO. I am really happy to see this being tackled in the Swift 3 timeframe.
>> Sent from my iPad
>>> On Apr 25, 2016, at 12:27 PM, Chris Lattner <clattner at apple.com> wrote:
>>> Hello Swift community,
>>> The review of "SE-0069: Mutability and Foundation Value Types" begins now and runs through May 4. The proposal is available here:
>>> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
>>> 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, 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 you 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
>>> Thank you,
>>> -Chris Lattner
>>> Review Manager
>>> swift-evolution-announce mailing list
>>> swift-evolution-announce at swift.org
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution