> On May 4, 2016, at 11:12, Joe Groff via swift-evolution > <[email protected]> wrote: > > I can see value in there being some kind of PureValue protocol, for types > that represent fully self-contained values, but conforming to that protocol > requires a bit more thought than just being a struct or enum, since there are > structs that have reference semantics (such as UnsafePointer), and there are > hybrid value types that contain references to data that isn't part of the > value (an Array<Class>, for instance). > > -Joe
+1 I'd think that both "PureValue" and "PureReference" would be useful. Isn't it the mixed types that make for tricky mutation rules & serialization? _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
