Andy Matuschak@andy_matuschak·Jun 22, 2015But you can make it work for your types! https://mikeash.com/pyblog/friday-qa-2015-04-17-lets-build-swiftarray.html…Quote TweetDavid Smith@Catfish_Man · Jun 22, 2015Reminder that copy-on-write in Swift is a feature of Array, Dictionary, etc… not of structs in general. It’s not automatic for your types.Show this thread21139
Nacho Soto@NachoSoto·Jun 22, 2015@andy_matuschak @Catfish_Man really!? so all this time, when we’ve been saying “value semantics”, they’re not equal for all value types?21
Andy Matuschak@andy_matuschakReplying to @NachoSoto@NachoSoto @Catfish_Man Huh? No, copy-on-write-ness is what’s different. That’s not part of semantics—it’s an optimization.8:53 PM · Jun 22, 2015·Tweetbot for Mac3 Likes
Zach Gotsch@CodeAthena·Jun 23, 2015Replying to @andy_matuschak@andy_matuschak @NachoSoto @Catfish_Man I do feel a little misled. Strange to learn this on Twitter rather than in a wwdc talk.21
David Smith@Catfish_Man·Jun 23, 2015@CodeAthena @andy_matuschak @NachoSoto I suspect the folks giving talks didn’t realize there was any confusion; I didn’t until recently.1