3 ms·
> and there's no reason not to do it the Rust way memcpy everywhere is definitely not the best answer to every problem
by jcelerier 6y ago
> and there's no reason not to do it the Rust way
memcpy everywhere is definitely not the best answer to every problem
- Ericson2314 6y agoIf you want a copy constructor, it would work like this: Copy : Clone :: Move : Relocate I.e. there would not be the presumption that everything is automatically movable or coppiable, there would be magic traits to indicate memmove / memcpy and friends, and then plain old stdlib super traits for user-defined cloning and relocating. This is the the right design for move constructors, full stop.
- FreeFull 6y agoIt's not like C++'s move semantics magically get rid of the necessity of copying data either.