tc39 proposal-extensions issues

tc39 / proposal-extensions

Extensions proposal for ECMAScript

MIT License

150 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Built-in extension functions

#17 andyearnshaw opened 1 week ago
5
Optional chaining for extensions -- `?::`

#16 andyearnshaw opened 1 week ago
4
Advancing proposal to stage 2 any time soon?

#15 gonzojive opened 2 months ago
1
Use cases of static invoking the lexical methods/accessors in the classes

#14 hax opened 2 years ago
0
Rename the proposal from "extensions" to "static dispatch operator"

#13 hax closed 1 week ago
1
Proposal iteration plan: remove auto adaption of util functions

#12 hax opened 2 years ago
0
Useful to Node.js Core

#11 bmeck opened 3 years ago
23
Potential hazard

#10 MadProbe opened 3 years ago
4
Why $::util:toSet() equals to toSet($) but not toSet.cal($) in README "Example of using constructors or namespace object as extensions"?

#9 LongTengDao opened 3 years ago
5
Why :: need to be used while defining?

#8 LongTengDao opened 3 years ago
19
Mark as stage 1

#7 saschanaz closed 3 years ago
1
Why is the way 'this' passed was in different way in NamespaceExtension and ConstructorExtension?

#6 mmis1000 opened 3 years ago
5
Tree shaking of imports?

#5 mmis1000 opened 3 years ago
1
Make shadowing an early error but not a new namespace

#4 Jack-Works opened 3 years ago
14
Redocument this proposal better

#3 Jack-Works opened 3 years ago
1
Relation with The Pipeline Operator

#2 Huxpro opened 3 years ago
9
Action required: Greenkeeper could not be activated 🚨

#1 greenkeeper[bot] closed 4 years ago
0