-
Notifications
You must be signed in to change notification settings - Fork 482
ASoA: Apply rule of five #14905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
ASoA: Apply rule of five #14905
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
| return this->desc_hash == _desc_hash; | ||
| } | ||
|
|
||
| constexpr ~TableRef() = default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a trivial struct that does not require a destructor. Since it contains three integers, for which move and copy identical, there is no need to declare everything else as well.
| } | ||
|
|
||
| ColumnIterator() = default; | ||
| ~ColumnIterator() = default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, the destructor only makes sense for the things that own dynamically allocated memory directly, especially if there is a polymorphic hierarchy. This class only contains observer pointers, so there is really no need for the move constructors either.
|
I am not sure this is a good idea. Have you checked with bloaty this change does not add to the already large number of symbols we have? Is this trying to solve an actual problem or you simply want to have the linter happy? |
I haven't but I'm happy to check if you point me to instructions.
Both.
|
noexcept.TableIteratornot defined as it cannot be defaulted.