On Apr 8, 2011, at 2:48 AM, David Bruant wrote: > Like today, no worries to monkey-patch the behavior for regular objects, > but people will expect this method to have the correct behavior on > proxies too. Which means having a mechanism to call the "fix" trap (with > a way to distinguish call cases as suggested in > https://mail.mozilla.org/pipermail/es-discuss/2011-April/013577.html ?) > and to fix the proxy (TypeError||become). Without the distinction part, > Object.preventExtension fits the job. With the distinction part, a > Proxy.trap + Proxy.fix (or equivalent mechanisms) may be necessary.
It's a good point, but my conclusion, or assumption really, was that we wouldn't add any more Object.* methods to clear [[Extensible]]. It doesn't seem worth it, and your point is a good reason to actively avoid such additions. Any other reason for a way to call fix explicitly? /be _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
