News for hackers. Stuff that matters.

A comment on GCC 11.1. Parent comment

Re:GCC 11.1 by jcelerier on Tuesday April 27, 2021 @01:55PM (#26959220)
> and there's no reason not to do it the Rust way

memcpy everywhere is definitely not the best answer to every problem

[ Parent | on HN ]
Re:GCC 11.1 by Ericson2314 on Tuesday April 27, 2021 @03:56PM (#26960698)
If 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.

[ Parent | on HN ]
Re:GCC 11.1 by FreeFull on Tuesday April 27, 2021 @04:29PM (#26961103)
It's not like C++'s move semantics magically get rid of the necessity of copying data either.
[ Parent | on HN ]