Looking at #9365, it looks like this is to enable Java collections to be used in an API that is exposed to JS. The JS code could then use the collections using a subset of the Java API. As apposed to making the Java Collections look like native Java arrays for example.
On Friday, June 17, 2016 at 11:18:14 AM UTC-4, Thomas Broyer wrote: > > > > On Friday, June 17, 2016 at 4:15:00 PM UTC+2, Paul Stockley wrote: >> >> The question I have is more general. What will the scope of Elemental 2 >> be? Will it include collections and json support like elemental or will it >> be just an interface to browser API's? >> > > With https://github.com/gwtproject/gwt/issues/9365 (not sure what it > actually means though, I might be wrong) and > https://github.com/gwtproject/gwt/issues/9364, I don't think you'd need > elemental.json anymore (given that String, Double and Boolean directly map > to JS String, Number and Boolean). The former might also remove the need > for elemental.util "collections". > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/74b0f8b7-cd78-47a8-9ac6-1c58d71a12f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
