This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
Issues: tc39/proposal-static-class-features
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
ClassDefinitionEvaluation does not correctly restore outerPrivateEnvironment.
#68
by rbuckton
was closed Jan 27, 2021
Specification text for this proposal and class fields proposal is out of sync
#67
by rbuckton
was closed Jan 27, 2021
Should we disallow static method definitions whose PropName is "prototype" or "constructor"?
#60
by JLHwung
was closed Jun 8, 2020
RS ClassDefinitionEvaluation, step 34.a. looks incorrect
#57
by Andrew-Cottrell
was closed Oct 7, 2019
Missing early error restriction for accessors with different placement, but same private name
#48
by anba
was closed Sep 13, 2019
Should static public fields be coupled with static private fields and methods?
#28
by littledan
was closed May 11, 2018
Impressions from the January 2018 TC39 meeting and next steps
#25
by littledan
was closed Jun 9, 2018
Preference for
static {} block to perform privileged static initialization
#23
by rbuckton
was closed May 12, 2018
local lexical declarations should not be in scope for extends clause
#21
by allenwb
was closed Jan 24, 2018
Should class body lexical function declarations create const bindings?
#20
by allenwb
was closed Jun 9, 2018
Should only
function be supported in classes, and not other lexical declarations?
#17
by littledan
was closed Oct 11, 2018
Replace lexically scoped functions in classes with private names defined outside of classes?
#16
by littledan
was closed Oct 11, 2018
Is it excessive to have both private methods and lexically scoped functions in classes?
#15
by littledan
was closed Jun 9, 2018
Clarify in explainer that <placeholder> will be filled in with a token
#14
by littledan
was closed Jan 17, 2018
What should be the scope that a lexical declaration is evaluated in?
#13
by littledan
was closed Oct 11, 2018
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.