[
https://issues.apache.org/jira/browse/THRIFT-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196413#comment-15196413
]
Jens Geyer commented on THRIFT-3705:
------------------------------------
You were on the right track. However,. it is not the map {{typedef}},it is the
implicit {{typedef}} produced by the parser when it hits an yet unknown type in
the IDL. Fully reproducible with this (note the absence of typedefs)
{code}
// Generating the following IDL results in Go code which does not compile:
struct Foo2 { 1: map<Foo, Foo> theMap }
struct Foo {}
// However, if the declaration of the key/value type precedes usage, the code
is generated correctly:
struct Bar {}
struct Bar2 { 1: map<Bar, Bar> theMap }
{code}
> Go map has incorrect types when used with forward-defined types
> ---------------------------------------------------------------
>
> 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)
