You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Can Celasun (JIRA)" <ji...@apache.org> on 2017/05/30 12:02:04 UTC

[jira] [Closed] (THRIFT-3553) Go Map value type is dependent on order of entity definitions

     [ https://issues.apache.org/jira/browse/THRIFT-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Can Celasun closed THRIFT-3553.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.0

This was indeed fixed by THRIFT-3705. I have a runnable sample [here|https://github.com/dcelasun/misc/tree/master/thrift/THRIFT-3553].

> Go Map value type is dependent on order of entity definitions
> -------------------------------------------------------------
>
>                 Key: THRIFT-3553
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3553
>             Project: Thrift
>          Issue Type: Bug
>          Components: Go - Compiler
>            Reporter: Matt Sanders
>            Priority: Minor
>              Labels: golang, thrift
>             Fix For: 0.10.0
>
>
> Deserialization code of map type properties will generate a compilation error if the type definition of the value appears after the definition of the map where it is used.
> {code:title=Error Example}
> struct TestsResponse {
> 	1: map<string, Test> tests
> }
> struct Test {
> 	1: string id
> 	2: string name
> }
> {code}
> Compilation Error
> {quote}
> ttypes.go:83: cannot use _val1 (type *Test) as type Test in assignment
> {quote}
> In the example moving the definition of 'Test' to appear before 'TestResponse' avoids the compilation error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)