Closed
Bug 1633767
Opened 5 years ago
Closed 5 years ago
Enable prototype private fields functionality under a configure option
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
INVALID
People
(Reporter: mgaudet, Assigned: mgaudet)
References
Details
Attachments
(2 obsolete files)
No description provided.
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•5 years ago
|
||
With --enable-private-fields, this stops us from immediately producing an error at a
private identifier.
Depends on D72952
|
||
Updated•5 years ago
|
Priority: -- → P2
|
|
||
Updated•5 years ago
|
Attachment #9144146 -
Attachment is obsolete: true
|
|
||
Updated•5 years ago
|
Attachment #9144145 -
Attachment is obsolete: true
|
|
Assignee | |
Comment 3•5 years ago
|
||
Instead going to add a runtime switch for this.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•