Github user jeking3 commented on the issue:

    https://github.com/apache/thrift/pull/1119
  
    @bgould Generated code should always be explicitly fully pathed or 
namespaced and never make any assumptions.  Thrift already uses namespaces so I 
would have no problem with org.king.Object as a thrift structure so long as it 
derives from java.lang.Object.  If the code generator uses "Object" without 
qualifications that could be ambiguous, and that is a valid defect .. I like 
the idea of eliminating that.  With regards to using a structure named Object, 
well that's really up to the folks using thrift, it isn't up to the thrift 
project to tell them how to name their structures and we should stay out of 
their way where we can.


---
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.
---

Reply via email to