Re:Writing Good C++14 by Default [pdf]
by AnimalMuppet on Wednesday September 23, 2015 @12:50PM
(#10266189)
Which, if we were talking about Rust here, might be relevant. But in this thread of the conversation, we're talking about C++ operator overloading and why you need it for deep copying on assignment. In the immediate context, how Rust does it is not relevant.
[ Parent
| on HN ]
Re:Writing Good C++14 by Default [pdf]
by dbaupp on Wednesday September 23, 2015 @07:00PM
(#10268842)
The discussio is about strategies to avoid the double-frees problem in a hypothetical "C++ with changes", and Rust's is one example. Seems fine and useful to give examples. (That's what Gankro's comment is too: Rust's strategy is affine types.)
Re:Writing Good C++14 by Default [pdf]
by AnimalMuppet on Wednesday September 23, 2015 @07:18PM
(#10268913)
Could be I missed something, but I looked all the way back to the root of this thread, and I didn't see (in any of the direct ancestors) anywhere where the topic was a hypothetical "C++ with changes".