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

copy/move ctor #6

Open
tvaneerd opened this issue Jul 20, 2017 · 0 comments
Open

copy/move ctor #6

tvaneerd opened this issue Jul 20, 2017 · 0 comments

Comments

@tvaneerd
Copy link
Owner

It should probably be mentioned that the copy/move ctor should never be explicit.

And by 'never' does mean 'rarely' (as usual) or does it really mean never?

A heavy class, ie an Image class should probably not have a copy-ctor.
Typically a copy() or clone() function makes it more clear than there is no free lunch.
Would an explicit copy-ctor actually make sense here?

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

No branches or pull requests

1 participant