Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1083
I can see cases where someone relying on the enumeration's numeric output
today would have a breaking change that they cannot easily avoid here. Changes
like this one, for example the one that added what() to thrift C++ generated
exception code, have caused me headaches in the past when upgrading. This
makes me wonder if we want to make things like this thrift-compiler-time
optional. Not something we have to solve here, but a more general question to
the maintainers.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
