> On Aug 1, 2016, at 7:24 PM, Rick Mann <rm...@latencyzero.com> wrote:
>
> But my model has implicit reference semantics: multiple instances of a part
> can share a PartDefinition; it is intended that if the PartDefinition
> changes, all the referencing instances get the change.
Bingo. That’s the very definition of a reference.
> On Aug 1, 2016, at 7:18 PM, Jack Lawrence <ja...@apple.com> wrote:
>
> I’d think that value semantics would be the right choice here. When you do a
> mutation, you would copy the state of the entire diagram. It should be
> efficient via COW
It sounds like you’re talking about a persistent data structure
<https://en.wikipedia.org/wiki/Persistent_data_structure>, which to me is not
the same thing as a value type.
—Jens
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
