Mixed types would be the problem - that's why objects within the List/Map have types embedded within them.
On Mon, Sep 11, 2017 at 12:01 PM, Robert Dale <[email protected]> wrote: > I'm not sure that's feasible since any list or map could contain mixed > types. Maybe I don't understand the use case. > > Robert Dale > > On Mon, Sep 11, 2017 at 11:27 AM, Jorge Bay Gondra < > [email protected] > > wrote: > > > Hi, > > The new GraphSON3 g:List, g:Set and g:Map definitions are an improvement > > over js arrays and associative arrays, but they doesn't provide the child > > type information. > > > > We could add support for chid type info, something like > > "g:List<g:Traverser>" or "g:Map<g:Int32,g:Vertex>". > > > > For typed languages, it would allow compile time checks. > > For any technology, it would more user-friendly error messages ("Expected > > Vertex, obtained..."). > > > > Jorge > > >
