It is difficult to use by its nature, it's the kind of thing that implementors or maybe library authors would make use of. It exposes a hook for what previously was a low level spec operation (the object allocation part of construction).
On Wed, Jan 16, 2013 at 7:34 PM, Nathan Wall <nathan.w...@live.com> wrote: > > In this light, it may also make sense to make Function.prototype.@@create > and > > Function.prototype.@@hasInstance non-writable, non-configurable. > > Regardless of the defaults, SES could presumably defend itself in the > > same same way. > > If you make Function.prototype.@@create non-writable, wouldn't that make > it difficult to use? > > I'm thinking of the "you can't override non-writable inherited properties > with a write operation" ES5 decision, thus forcing you to use > Object.defineProperty. > > Nathan
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
