Fix plain map() test case, it broke because of new real world compatible
map() trailing non-existent elements behavior. Add more cases to the
specific test case for trailing elements.
The real world behavior is to call the user callback only for elements
that exist, and to count any trailing non-existent elements into the
result array length.
Update the known issues for test262 suite:
- 1 new enumeration test failed, added bug testcase for it
- 1 new property setter test failed, due to Duktape's extra setter argument
(property name) which the test case tests for specifically
- 2 new test failures related to current 2G array limit
A lot of E6 tests have been added to test262; those were all marked "known
issues" so that they're not counted as actual errors to fix.
Remove end line tracking from lexer tokens. The end line information is
not used at the moment, and there doesn't seem to be a reason to use it
in the near future either.
Change default behavior of Array.prototype.concat() to match (apparently
non-standard) real world behavior of at least V8, Rhino, and Spidermonkey:
When the concat result contains trailing non-existent elements, the E5.1
behavior is to not count them towards the 'length' of the concat result.
The real world behavior is to include them in the result 'length'.
Disable fast returns for 1.0 release: they have quite a small speed impact
(10-15%) at present and return handling (and other call handling code) needs
a review anyway.
This feature needs some more thought and has somewhat minimal performance
impact at present (10-15%) over the longjmp path. The better approach may
be to handle every return as a "fast return" and fall back to a longjmp in
special cases like thread yields and such.