I have just seen you change the design 3 times with the drop of a hat every time some one mentions a new type of code flow.
And there's no guarantee that tomorrow you won't change it again once you remember something else.
And don't think you have a solid grasp on what your proposal exactly is.


-----Original Message-----
From: Std-Proposals <std-proposals-bounces_at_lists.isocpp.org> On Behalf Of Frederick Virchanza Gotham via Std-Proposals
Sent: Friday, July 19, 2024 00:54
To: std-proposals_at_[hidden]cpp.org
Cc: Frederick Virchanza Gotham <cauldwell.thomas_at_gmail.com>
Subject: Re: [std-proposals] Stop gap required for NRVO until Anton's paper is assimilated

On Thu, Jul 18, 2024 at 4:15 PM Frederick Virchanza Gotham wrote:
>
> I have implemented this on the four main compilers, Microsoft VC++,
> GNU g++, LLVM clang, Intel ICX:
>
> https://msvc.godbolt.org/z/6P7xKdn1T
>
> It still works if you turn on the most extreme optimisations.


I have integrated the above GodBolt into the paper's main GodBolt:

    https://msvc.godbolt.org/z/vq9r5Exz1

Previously there were 4 functions:

* std::construct_modify
* std::construct_modify_with_tuples
* std::invoke_modify
* std::invoke_modify_with_tuples

And now there's a 5th function:

* std::construct_modify_retry

The fifth function is the one that can do loops. Maybe there should also be "invoke_modify_retry". And perhaps also "construct_modify_retry_with_tuples" and "invoke_modify_retry_with_tuples".
--
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals