There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
If I call ArrayInstance.Construct with an single (number) argument I get back an array with the length 1, but no elements filled in. But actually I wanted to create an array with exactly this element.
The issue comes from jurassic only having a single overload which uses a params parameter, so it cannot tell the difference between passing in an array or passing in a single int.
In a browser (testable with the firefox debugging tools) it makes a difference wether I call new Array(1) or new Array(). First one is the behaviour jurassic provides, second is the one which I cannot achieve with the Construct method.
Workaround is to use New() rather than Construct() but this still is very confusing (and time consuming to find).