I have a small class that has some data members. I just implemented the copy & assignment constructors manually because I want those to leave some members out when a class instance is to be copied from. This felt like a quirky exception from the rule of three, but I'm not really managing a resource, so I don't think I'm strictly breaking it.
Anyway, my question is: Is there perhaps a built-in way to "tag" some class members to not be copied over in the default implementations of copy & assignment constructors? Kind of like for example you can mark a member "volatile" (or was it "mutable"?) and it will be editable even if the object reference is const. And if no, why, and is there a better way of doing what I'm currently doing?
Note: I'm talking form a C++14 perspective, and yest I know the rule of three is the rule of 5 now, but I haven't got around to implementing those yet, and am not really sure if I'll need to.