> 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 [email protected] https://mail.mozilla.org/listinfo/es-discuss
