Date: Sat, 5 Jul 2025 11:22:22 -0400
This is a reasonable next step, since trivial relocation, as defined by C++26, will differ significantly from the de facto implementation practice that has been in place for years.
> On Jul 2, 2025, at 10:58 AM, Giuseppe D'Angelo via Std-Proposals <std-proposals_at_[hidden]> wrote:
>
> Hi,
>
> I plan to submit
>
> https://isocpp.org/files/papers/D3780R0.html
>
> in the next mailing. It's about a type trait to detect bitwise trivial relocability. This detection has (IMHO) huge applicability and also offers a direct upgrade path for libraries that today have their in-house definition of "trivial relocation" likely meaning "bitwise", and want to avoid possible surprises if they just switch to C++26's definition of TR.
>
> Any comment is very much appreciated.
>
> Thank you,
> --
> Giuseppe D'Angelo
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
> On Jul 2, 2025, at 10:58 AM, Giuseppe D'Angelo via Std-Proposals <std-proposals_at_[hidden]> wrote:
>
> Hi,
>
> I plan to submit
>
> https://isocpp.org/files/papers/D3780R0.html
>
> in the next mailing. It's about a type trait to detect bitwise trivial relocability. This detection has (IMHO) huge applicability and also offers a direct upgrade path for libraries that today have their in-house definition of "trivial relocation" likely meaning "bitwise", and want to avoid possible surprises if they just switch to C++26's definition of TR.
>
> Any comment is very much appreciated.
>
> Thank you,
> --
> Giuseppe D'Angelo
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
Received on 2025-07-05 15:22:36