Incorrect behavior (and decompilation) when sharps are nearby

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 1 bug, {testcase})

Trunk
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
This was caught by jsfunfuzz round-trip checking.

js> (function() { var a = [1,,,]; return a; })()              
[1, , ,]
Correct

js> (function() { var a = [1,,,]; return a; })                
(function () {var a = [1, , , ];return a;})
Correct

js> (function() { var a = [1,,,]; return a; var b = #1#; })() 
[1]
Missing all the holes

js> (function() { var a = [1,,,]; return a; var b = #1#; })
(function () {var a = [1, , ];return a;var b = #1#;})
Missing one of the holes
OS: Mac OS X → All
Hardware: x86 → All
Fixed by bug 566700, the removal of sharp variables.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.