Skip to content
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

[lipstick] Use default copy assignment operator for NotificationList. JB#60722 #46

Merged
merged 1 commit into from Jan 24, 2024

Conversation

mlehtima
Copy link
Contributor

@mlehtima mlehtima commented Dec 7, 2023

No description provided.

Copy link
Member

@monich monich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could copy constructor be default too?

@mlehtima
Copy link
Contributor Author

mlehtima commented Dec 7, 2023

I was wondering if the custom copy constructor is really needed or not. If it's not needed then we can just remove that instead defining default copy assignment operator.

@monich
Copy link
Member

monich commented Dec 7, 2023

I'm not sure whether or not that would affect ABI (which probably doesn't matter anyway)

Copy link
Contributor

@pvuorela pvuorela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit curious on these what's making the explicitly defined operator needed, but the change itself should be ok. Wouldn't hurt having the rationale mentioned in commit message either.

… JB#60722

Implicitly-declared copy assignment operator is deprecated in C++11 when
user-declared copy constructor exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants