Source type inference is overriden by serialized type information

[Gabriel-Darbord]

Example origin:

Map<String, String> foo() { /* ... */ }

Example serialized value:

{ "@type": "HashMap" }

The type inference ends up being HashMap and argument types (String) are lost.

[Gabriel-Darbord]

Actually we want this behavior, however what we're missing are the type parameters of the concrete type.
In the example given above, it is correct to have an HashMap instead of a Map, however the <String, String> information is missing.
At some place, at some time, the value's concrete type and the code's type parameters should be used together to obtain the right type: HashMap<String, String>.