Closed
Bug 1562054
(private-fields)
Opened 5 years ago
Closed 3 years ago
[Meta] Ship Private fields proposal
Categories
(Core :: JavaScript Engine, enhancement, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: khyperia, Assigned: mgaudet)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
(Keywords: dev-doc-needed, meta, parity-chrome)
Other relevant bugs:
bug 1499448 - public fields (completed)
bug 1535804 - public static fields
Updated•5 years ago
|
Keywords: parity-chrome
Updated•5 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Updated•5 years ago
|
Alias: private-fields
Assignee: nobody → mgaudet
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Re-summarying as we will close this bug when we ship private fields.
Summary: Implement private instance fields proposal → [Meta] Ship Private fields proposal
Comment 2•4 years ago
|
||
For everyone following along. This is currently mainly blocked by bug 1662559.
Comment 4•4 years ago
|
||
Bug 1708235 actually shipped private fields.
Updated•4 years ago
|
Assignee | ||
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•