[ https://issues.apache.org/jira/browse/THRIFT-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180083#comment-15180083 ]
ASF GitHub Bot commented on THRIFT-3705: ---------------------------------------- Github user tylertreat commented on the pull request: https://github.com/apache/thrift/pull/918#issuecomment-192341673 This appears to be an issue with forward usages of types, but I haven't been able to figure out a proper solution. Closing for now... > Go map incorrect types with map typedef > --------------------------------------- > > Key: THRIFT-3705 > URL: https://issues.apache.org/jira/browse/THRIFT-3705 > Project: Thrift > Issue Type: Bug > Components: Go - Compiler > Reporter: Tyler Treat > Assignee: Jens Geyer > Priority: Minor > > Generating the following IDL results in Go code which does not compile: > {code} > typedef map<Foo, Foo> FooMap > struct Foo {} > service Service { > void foo(1: FooMap fooMap) > } > {code} > ./service.go:278: cannot use _key4 (type *Foo) as type Foo in map index > ./service.go:278: cannot use _val5 (type *Foo) as type Foo in assignment > However, if the struct precedes the typedef, the code is generated correctly: > {code} > struct Foo {} > typedef map<Foo, Foo> FooMap > service Service { > void foo(1: FooMap fooMap) > } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)