[swift-evolution] [RFC] "Library Evolution Support in Swift ('Resilience')"
jgroff at apple.com
Wed Feb 10 15:02:40 CST 2016
> On Feb 10, 2016, at 1:00 PM, David Owens II via swift-evolution <swift-evolution at swift.org> wrote:
> Actually, there are quite a few places that allow for the same type of behavior: @inlineable, accessors, enums, structs, etc...
Of these, inlineable functions definitely have the same problem, but I'm not sure what you're referring to with regard to accessors, enums, or structs. These will all be accessed by opaque interfaces (unless declared fixed-contents), so clients are guaranteed to use the framework implementation.
> As soon as I see these words: "existing clients may use the new implementations, or they may use the implementations from the time they were compiled, or a mix of both" or similar, we've ventured right back into undefined territory.
> That concerns me.
>> On Feb 10, 2016, at 12:45 PM, David Owens II via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> On Feb 8, 2016, at 6:24 PM, Jordan Rose via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>> This last point is a specific case of a general tenet of Swift: the default behavior is safe. Where possible, choices made when an entity is first published should not limit its evolution in the future.
>> Regarding this:
>>> Changing or removing a default value is permitted but discouraged; it may break or change the meaning of existing source code.
>> Maybe I'm being dense, but how is something with a caveat of "discouraged" and "it may break or change" in-line with "the default behavior is safe"? I've got no qualms with putting the default value in the client code; I actually think that is fine.
>> However, my concern is that you will have different behavior depending on if you simply drop in the updated binary vs recompile against the binary. Even worse if you have multiple components within your app that link against the library. If only one of those components is recompiled on release, you now have a problem of conflicting behavior within your own app because of the client-side calling the API will be using different values.
>> It would seem that removing the default value could be permitted (though maybe still discouraged) because this will result in a compiler error in the scenario above. It's still possible to have different behavior in your components, but now it's no longer implicitly happening. However, changing the default parameter seems highly problematic.
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto: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