Date: Tue, 17 May 2022 18:37:42 -0700
On Tuesday, 17 May 2022 18:16:14 PDT Edward Catmur via Std-Proposals wrote:
> So (1) and (2) always apply; ABI is dependent on whether a class is
> trivially or user relocatable (and the language on callee-destroy will need
> amending). Since you're specifying that classes with synthesized relocate
> (from move+destroy) are destroyed at the end of scope, the behavior for
> function parameters will be uniform with that for variables.
That's not a deal-breaker, but it's the next best thing. If adding this member
changes the ABI, then it won't be added for a lot of code that needs to retain
compatibility, including std::unique_ptr.
> So (1) and (2) always apply; ABI is dependent on whether a class is
> trivially or user relocatable (and the language on callee-destroy will need
> amending). Since you're specifying that classes with synthesized relocate
> (from move+destroy) are destroyed at the end of scope, the behavior for
> function parameters will be uniform with that for variables.
That's not a deal-breaker, but it's the next best thing. If adding this member
changes the ABI, then it won't be added for a lot of code that needs to retain
compatibility, including std::unique_ptr.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Received on 2022-05-18 01:37:43