Re:GCC Preparing to Introduce “-Fhardened” Security Hardenin...
by gpderetta on Tuesday September 19, 2023 @03:01PM
(#37574668)
I have to try that. There are defect reports for corner cases.
In any case this is also allowed:
T val = T();
And copy elision is now guaranteed.
Re:GCC Preparing to Introduce “-Fhardened” Security Hardenin...
by tsimionescu on Wednesday September 20, 2023 @02:11AM
(#37580923)
The example looks like this:
class A {
protected:
A() {}
}
class B : public A {}
B x; //ok
B y{}; //not ok, can't access A::A()
Would the T val = T(); example work if you don't have a copy constructor at all, or no move constructor, or custom ones which do weird things?
Re:GCC Preparing to Introduce “-Fhardened” Security Hardenin...
by gpderetta on Wednesday September 20, 2023 @04:46AM
(#37581930)
Played it a little bit: this seems to be a regression and breaking change from C++14 where B would not be an aggregates, so B{} would just invoke the default constructor. This is probably an oversight, I wonder if there is a Defect Report.
edit: it works by making the inheritance protected, as B is no longer an aggregate. The right fix would be to also disqualify B from aggregate status if the base class constructor is unreachable.
Also making both A and B non-empty removes aggregate status, so it is really a dark corner of the language.
Overall I think it's safe to say that the two syntaxes have different semantics, even if they overlap in most cases.