The case against it is it only works with primitives. If you set an object/array on the prototype it's shared by all instances, which is dangerous.
On Fri, Dec 12, 2014 at 10:15 PM, Glen Huang <[email protected]> wrote: > I agree data properties on the instance prototype is a bad idea. But > static properties are really useful. Could we at lease allow them: > > class Foo { > static bar = 43; > } > > On Dec 13, 2014, at 12:53 PM, Kevin Smith <[email protected]> wrote: > > function Foo() {} >> Foo.bar = 1; >> Foo.prototype.baz = 2; >> >> Is it possible to allow this in es6 with the class syntax? Or it belongs >> to es7? Or it’s simply a terrible idea? >> > > Data properties on the instance prototype are generally considered to be a > footgun. If you want to expose a data-like property on the constructor (or > the instance prototype), you can use accessors: > > let _bar = 1; > class Foo { > static get bar() { return _bar; } > static set bar(value) { _bar = value; } > } > Foo.bar = 43; > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss

