Github user jeking3 commented on the pull request: https://github.com/apache/thrift/pull/798#issuecomment-173236071 I'm a fan of const correctness. We shouldn't penalize const correctness due to an inherent weakness in the language (that was resolved in C++11, i.e. the [override operator](http://en.cppreference.com/w/cpp/language/override)). I agree this would be something to list as part of a release's "breaking changes" which would affect customer created subclasses.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---