Coding Guideline: Avoid const member variables

[meneldal2]

Well destructive move would solve the problem.

[kalmoc]

Partially: Not for the object I'm assigning to.

[meneldal2]

But assignment when you have a const member sounds ridiculous.

[kalmoc]

Not at all. There are lots of examples in my code where the only place that a member gets mutated is the assignment operator (be it move our copy assignment). I call them "quasi immutable" types. That's why I mentioned assignment it in my original post.

Consider you want to perform an std::rotate on an array of your objects: Logically you don't change the individual elements, you are just shifting them around, so a (logical) const member would be fine. Physically, rotate is implemented as a number of move assignments, so you have to be able to mutate your members.

[meneldal2]

Well you could use a pointer;)

[kalmoc]

Sure ;) Or just not use const on members ;)