Github user jparise commented on the issue:
https://github.com/apache/thrift/pull/1474
I'm not affiliated with either project, but I work in an environment that
uses multiple Thrift implementations, so interoperability is important to us.
We're specifically interested in using some of these new codes (e.g.
`LOADSHEDDING`) between services, and I think there's value in achieving error
code parity. Likewise, if Apache Thrift had been the first to introduce these
new error codes, I'd be making the same case for their inclusion in fbthrift
and other implementations.
I don't know if it's important to establish a plan for "approving" new
error codes going forward. When I wrote "guarantee no future conflicts" in the
summary, I meant that these particular values (11, 12, 13) have already been
effectively allocated by fbthrift, and adding them to Apache Thrift eliminates
the chance that those indices are ever assigned to different, conflicting codes
in this project.
---
