wrong error on destructing assignment

[dimitriylol]

• Version: v6.3.0
• Platform: Linux dlyman 4.4.0-53-generic may be it's good idea go tell something about this fork? #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
• Subsystem:

Destructuring assignment array on object instance produces a TypeError with an incorrect message.
Code that demonstrates the problem:

function foo () { return { a: 10 }; }
const [ first, second ] = foo();

TypeError: foo is not a function
    at repl:1:27
    at sigintHandlersWrap (vm.js:32:31)
    at sigintHandlersWrap (vm.js:96:12)
    at ContextifyScript.Script.runInContext (vm.js:31:12)
    at REPLServer.defaultEval (repl.js:308:29)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:489:10)
    at emitOne (events.js:101:20)
    at REPLServer.emit (events.js:188:7)

Please, clarify, is it possible to produce error without mentioning function name?

[jasnell]

That is quite odd. Chrome does the exact same thing so it's definitely a V8 thing. Whether or not it's a bug or intended behavior we'll have to leave it for the @nodejs/v8 team to figure out. @fhinkel thoughts?

[fhinkel]

var [ x, y ] = {a: 10}
Uncaught TypeError: undefined is not a function
    at <anonymous>:1:1

Oh yes, the error message is not helpful. Something like {a:1} is not iterable would be much better. @dimitriylol thanks for reporting! Do you mind heading over to V8's issue tracker and reporting it there?

[dimitriylol]

@fhinkel I created issue 5973 on V8's issue tracker.
Thanks for quick response.