> ... - and the fact that you can destructively move from a mutable
reference in a called function is a footgun for the actual owner of the
object which will still call the constructor.

You can also just destroy the object via a mutable reference, I don't see
this argument as that strong, we would just need to treat
destructive move with same care as obj.~Class() .


On Fri, Dec 27, 2024 at 1:31 PM Thiago Macieira via Std-Proposals <
std-proposals_at_[hidden]> wrote:

> On Friday 27 December 2024 08:30:31 Brasilia Standard Time Oskars Putans
> via
> Std-Proposals wrote:
> > My proposal isn't meant to solve these issues. It is merely a step in
> that
> > direction. What i'm proposing is an optional specialization for handling
> > prvalues in a way that doesn't require the moved from value to be in a
> > valid state.
>
> How does it mesh with the current object relocation proposals?
>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> Principal Engineer - Intel DCAI Platform & System Engineering
>
>
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>