Giters
tc39
/
proposal-rm-builtin-subclassing
Remove ES6 built-in subclassing
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
23
Watchers:
21
Issues:
18
Forks:
5
tc39/proposal-rm-builtin-subclassing Issues
Misleading proposal name?
Updated
a year ago
Comments count
7
It will break the web
Updated
3 years ago
Comments count
29
Type II support for promise `then` is essential for hooking into existing promises' lifecycles and observing them without a massive amount of complexity.
Updated
3 years ago
Comments count
4
Additional complexity you could remove from Promises
Updated
3 years ago
Comments count
17
"Have a good time"
Updated
3 years ago
Comments count
1
Should Type IV subclassing restrictions also apply to non-RegExp classes?
Updated
3 years ago
Comments count
1
In defense of Type II
Updated
3 years ago
Comments count
9
Type IV subclassing is largely orthogonal to other types; should it partake in the exit criteria?
Updated
3 years ago
Comments count
1
Moving this to TC39
Closed
4 years ago
Comments count
1
Deprecate `Symbol.species`
Updated
4 years ago
Comments count
5
Why not delegate to `this.constructor`
Updated
4 years ago
Comments count
1
Clarify or fix derived class constructors in the examples
Closed
4 years ago
Comments count
8
Leave IsRegExp out of this?
Closed
4 years ago
Comments count
3
Editorial suggestion: Explain what stays the same in the README
Closed
4 years ago
Comments count
5
What is the difference between Type 2 and Type 3?
Updated
4 years ago
Comments count
4
Semantics suggestion: Use SpeciesConstructor just for new.target
Updated
4 years ago
Comments count
9
Ambiguity about what this does for static methods in subclasses
Closed
4 years ago
Comments count
1