tc39/proposal-static-class-features
The static parts of new class features, in a separate proposal
HTML
Issues
- 5
Access from this should be supported
#62 opened by earonesty - 6
- 2
- 3
- 1
- 6
- 0
Mention static private accessors?
#61 opened by rauschma - 3
Should we disallow static method definitions whose PropName is "prototype" or "constructor"?
#60 opened by JLHwung - 1
- 4
Missing early error restriction for accessors with different placement, but same private name
#48 opened by anba - 7
- 7
- 0
Mention acorn support
#39 opened by adrianheine - 13
Request for use cases for static public fields
#27 opened by littledan - 18
Should only `function` be supported in classes, and not other lexical declarations?
#17 opened by littledan - 4
Replace lexically scoped functions in classes with private names defined outside of classes?
#16 opened by littledan - 3
- 32
Should lexical declaration evaluation be before, after, or interleaved with static public fields?
#12 opened by littledan - 24
- 70
- 6
Is it OK that this repo merges static public fields, static private fields, and static private methods?
#3 opened by littledan - 6
- 3
Spec: Static private methods?
#37 opened by rwaldron - 3
- 18
Is it excessive to have both private methods and lexically scoped functions in classes?
#15 opened by littledan - 3
- 29
Inheriting accessor-like semantics
#24 opened by jridgewell - 0
- 2
static inner class
#34 opened by rahbari - 2
Proposal incomplete?
#30 opened by waldemarhorwat - 17
- 11
Should static public fields be coupled with static private fields and methods?
#28 opened by littledan - 2
- 0
- 1
- 7
static destructuring
#6 opened by graingert - 3
Static class field inheritance issues
#5 opened by gibson042 - 12