issues
search
tc39
/
proposal-private-methods
Private methods and getter/setters for ES6 classes
https://arai-a.github.io/ecma262-compare/?pr=1668
345
stars
37
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Use export keyword
#36
riax
closed
6 years ago
2
this.#value vs #value - short form of writing
#35
lukaszpolowczyk
closed
6 years ago
2
How does the private fields interact with the Proxy?
#34
baptistemanson
closed
6 years ago
4
Utterly flummoxing development process...
#33
rdking
closed
6 years ago
1
Tooling implementation status
#32
vjpr
opened
6 years ago
3
Implementability without per-instance memory overhead
#31
domenic
closed
6 years ago
7
Don't put own methods on the prototype
#30
nicolo-ribaudo
closed
6 years ago
1
Are private own methods also defined on the prototype?
#29
nicolo-ribaudo
closed
6 years ago
1
Yet another approach to a more JS-like syntax
#28
zocky
closed
6 years ago
74
What are some use cases for private accessors?
#27
gsathya
closed
6 years ago
1
A runtime solution for private/protected fields in ES6.
#26
rdking
closed
6 years ago
6
Final change suggestion
#25
rdking
closed
6 years ago
4
Syntax change suggestion
#24
rdking
closed
6 years ago
35
Normative: Disallow private static methods
#23
littledan
closed
6 years ago
0
This proposal does not address the actually existing needs for private fields
#22
zocky
closed
6 years ago
5
What about protected methods, better declaration of private fields, private async functions, and destructuring?
#21
eddyw
closed
6 years ago
1
New, more JS-like syntax
#20
friendlyanon
closed
6 years ago
19
Clarify behavior of private static methods
#19
shicks
closed
6 years ago
1
Consider prototype chain walk for private get/set
#18
rbuckton
closed
6 years ago
3
Are properties defined after private methods?
#17
jridgewell
closed
7 years ago
3
Weird coalescing behaviors
#16
jridgewell
closed
7 years ago
2
InitializeInstanceElements is never invoked
#15
ajklein
closed
7 years ago
0
Review comments: 2.7 ClassDefinitionEvaluation
#14
ajklein
closed
7 years ago
1
ClassElementName : PrivateName evaluation fails to pass bindingName to NewPrivateName
#13
ajklein
closed
7 years ago
0
[Proposal] Independent private field
#12
Aqours
closed
6 years ago
4
Should private methods be writable?
#11
littledan
closed
6 years ago
25
Stop this proposal
#10
uyeong
closed
6 years ago
151
How is this represented in property descriptors?
#9
rektide
closed
6 years ago
8
Why not use private keyword instead of #?
#8
cathrinevaage
closed
6 years ago
7
Do we need private accessors?
#7
littledan
closed
6 years ago
6
Minor editorial fixes
#6
bakkot
closed
7 years ago
1
Should private methods be auto-bound?
#5
littledan
closed
6 years ago
4
Allowing access without invocation
#4
bakkot
closed
7 years ago
3
Editorial: how should private methods and accessors be specified?
#3
littledan
closed
7 years ago
2
Typo: Reference to private accessor should use #
#2
robpalme
closed
7 years ago
1
Should private methods and accessors type-check their receiver?
#1
littledan
closed
7 years ago
23
Previous