René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"varargs ambiguity with generics","articleBody":"```\n\u003e var Arrays = java.import('java.util.Arrays');  \n\u003e var list = Arrays.asList(['a', 'b']);\n\u003e list.toArray();\n[ [ 'a', 'b' ] ] // should be ['a', 'b'] !!\n```\n\nI haven't looked at the varargs handling code, but I'm assuming it's because of the ambiguity due to the `asList` method being generic (`List\u003cT\u003e asList(T... a)`) - there's no way to distinguish if the javascript Array being passed into Arrays.asList() is intended as a single value of type `T` or if it's intended as a `T[]`. \n\nAssuming that's the issue, we could detect this ambiguity and throw an error, requiring the javascript programmer to use apply when they want a javascript array to be 'spread' into a varargs generic function. \n\nDoes this make sense?\n\n(Btw, ES6 compiled by babel works just fine here with  `Arrays.asList(...arr);`).\n","author":{"url":"https://github.com/henridf","@type":"Person","name":"henridf"},"datePublished":"2015-12-03T06:55:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/285/node-java/issues/285"}