query: Is it bad to use const_cast to factor out getters?
positive_passages.docid: 6559
positive_passages.text: How do I remove code duplication between similar const and non-const member functions?
negative_passages.docid: 155911
negative_passages.text: Purpose of returning by const value?
negative_passages.docid: 120760
negative_passages.text: Why use static_cast(x) instead of (int)x?
negative_passages.docid: 13673
negative_passages.text: Why don't Java's +=, -=, *=, /= compound assignment operators require casting?
negative_passages.docid: 148229
negative_passages.text: C++ static const access through a NULL pointer
negative_passages.docid: 6003
negative_passages.text: Isn't the const modifier here unnecessary?
negative_passages.docid: 19125
negative_passages.text: What is the advantage of using dynamic_cast instead of conventional polymorphism?
negative_passages.docid: 12036
negative_passages.text: Does the 'mutable' keyword have any purpose other than allowing the variable to be modified by a const function?
negative_passages.docid: 32976
negative_passages.text: Why cast unused return values to void?
negative_passages.docid: 68515
negative_passages.text: Literal initialization for const references
negative_passages.docid: 145465
negative_passages.text: Why can't static_cast be used to down-cast when virtual inheritance is involved?
negative_passages.docid: 38483
negative_passages.text: "const correctness" in C#
negative_passages.docid: 112035
negative_passages.text: How come a non-const reference cannot bind to a temporary object?
negative_passages.docid: 68872
negative_passages.text: What are the use cases for having a function return by const value for non-builtin type?
negative_passages.docid: 78469
negative_passages.text: Is a closure for dereferencing variables useful?
negative_passages.docid: 31384
negative_passages.text: How to initialize a const field in constructor?
negative_passages.docid: 87005
negative_passages.text: Why must the copy assignment operator return a reference/const reference?