[ 
https://issues.apache.org/jira/browse/THRIFT-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227033#comment-15227033
 ] 

Jens Geyer edited comment on THRIFT-3776 at 4/5/16 8:05 PM:
------------------------------------------------------------

{quote}
Because of that you can't compile multiple thrift files with the same 
namespace. They will just overwrite each other.
{quote}

I don't like to tell you, but that's something you should not do. That will 
cause all sort and kinds of problems, not just with Go. Always use different 
namespaces for IDL files, never share a Thrift namespace across multiple Thrift 
IDL files. That's a sure recipe for disaster.

If you don't have any final comments I will close this as "by design". The 
alternative would be to provide a *working* fix for *every* language supported 
by Thrift today - a task which will probably require quite a bit of effort to 
get it right.


was (Author: jensg):
{quote}
Because of that you can't compile multiple thrift files with the same 
namespace. They will just overwrite each other.
{quote}

I don't like to tell you, but that's something you should not do. That will 
cause all sort and kinds of problems, not just with Go. Always use different 
namespaces for IDL files, never share a Thrift namespace across multiple Thrift 
IDL files. That's a sure recipe for disaster.

> Go code from multiple thrift files with the same namespace
> ----------------------------------------------------------
>
>                 Key: THRIFT-3776
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3776
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Go - Compiler
>    Affects Versions: 0.9.3
>            Reporter: artem antonenko
>
> Currently compiler puts all generated Go code into two files - ttypes.go and 
> constants.go. Because of that you can't compile multiple thrift files with 
> the same namespace. They will just overwrite each other.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to