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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.10.0
• Component/s: Go - Compiler
• Labels: golang thrift
• Assignee: Unassigned
• Reporter: Matt Sanders
• Created: 14/Jan/16 16:00
• Updated: 30/May/17 12:01
• Resolved: 30/May/17 12:01

Description

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.

Error Example

struct TestsResponse {
	1: map<string, Test> tests
}

struct Test {
	1: string id
	2: string name
}

Compilation Error

ttypes.go:83: cannot use _val1 (type *Test) as type Test in assignment

In the example moving the definition of 'Test' to appear before 'TestResponse' avoids the compilation error.

Issue Links

• is related to: THRIFT-3705 Go map has incorrect types when used with forward-defined types