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 113
Issues: tc39/proposal-class-fields
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Statement of our opinions on class fields and its related package of proposals
#329
opened Apr 19, 2021 by
zeldajay
Properties without initializers can create some headache in "real-world" scenarios.
#323
opened Oct 1, 2020 by
dfahlander
[Suggestion] Consider to use time proof solution with private and protected keywords
#315
opened Aug 4, 2020 by
redradist
Execution of initializer expressions is confusing in readme
documentation
#299
opened Mar 5, 2020 by
papb
Insufficient time allotted for acceptance testing
[[Define]]
semantics
#273
opened Oct 4, 2019 by
rdking
Do not hesitate to make design changes just because Chrome has shipped
#254
opened Jul 1, 2019 by
jhpratt
Treating the
#
as part of a .#
operator instead of as part of a field name #foo
.
#250
opened Jun 26, 2019 by
trusktr
Use [[Set]] by default, add
define
keyword. (was: TypeScript class fields have [[Set]] semantics.)
#248
opened Jun 17, 2019 by
trusktr
Early Error rules need to be referenced explicitly in PerformEval
#234
opened Apr 12, 2019 by
jorendorff
Previous Next
ProTip!
Adding no:label will show everything without a label.