A case for removing the seal/freeze/isSealed/isFrozen traps

medikoo medikoo+mozilla.org at medikoo.com
Fri Feb 15 03:31:55 PST 2013

David, that's great clarification, and indeed it looks a bit different from
that perspective.

Still the only use case I see for freezing/sealing whole object (the way it
works now) is when we expose some constant dictionary object on which each
property counts, and that's very rare use case.
I don't see much good in disallowing extensions to prototypes we expose.
it's not JS way. We can prevent accidental modifications of *existing* API's
but disallowing custom extensions is too restrictive and not friendly in my

View this message in context: http://mozilla.6506.n7.nabble.com/A-case-for-removing-the-seal-freeze-isSealed-isFrozen-traps-tp272443p272674.html
Sent from the Mozilla - ECMAScript 4 discussion mailing list archive at Nabble.com.

More information about the es-discuss mailing list