this post was submitted on 18 Jun 2023
8 points (100.0% liked)

C++

1763 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
farados@vlemmy.net
Nihili0@programming.dev
lysdexic@programming.dev
8
The move constructor that you have to declare, even though you don't want anyone to actually call it - The Old New Thing (devblogs.microsoft.com)
submitted 1 year ago by mercator_rejection@lemmy.world to c/cpp@programming.dev
3 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] burrito82@feddit.de 3 points 1 year ago (2 children)

What can you do? Declare the move constructor, but don’t implement it.

This sounds like a solution that warrants a big huge comment or the next guy to refactor will remove it and break stuff...

[–] caleb-vincent@kbin.social 2 points 1 year ago

That's how we would have to do non-copyable classes before C++11. Older code bases are still filled with unimplemented copy constructors and assignment operators with comments. If you were extra thorough they'd also be private. PC Lint hated both of those tactics.

[–] gracicot@discuss.tchncs.de 2 points 1 year ago

This is actually what I did. I declared it and left a comment to explain why it needed to be left unimplemented.