[swift-evolution] Should we rename "class" when referring to protocol conformance?
dabrahams at apple.com
Mon May 16 02:00:47 CDT 2016
on Sun May 15 2016, Tyler Fleming Cloutier <cloutiertyler-AT-aol.com> wrote:
>> This implies, therefore, that if salient attributes *define* the
>> immutability of the value type, then the public interface is not
>> guaranteed to be immutable, since it is allowed to include
>> non-salient attributes. For example, a vector’s capacity could
>> change at any time, by virtue of it being stored via a reference.
> John refers to this at 52:26 in the first video and mentions that this
> is not full value semantics.
Huh, maybe I don't agree with him as much as I thought. But I'll check
it out and see. Thanks for the reference.
More information about the swift-evolution