preventExtensions trap and its true/false protocol
jwalden+es at MIT.EDU
Sun Mar 31 12:17:09 PDT 2013
On 03/31/2013 11:02 AM, David Bruant wrote:
> From the developer perspective, this doesn't really add anything since it's already possible to throw from within the trap (and that's probably more explicit and clearer than returning false).
That puts the onus on the trap to throw the correct kind of error, right? Admittedly this should be easy enough to get right, but it is a slight bit of extra complexity, versus having the implementation throw the correct error in one central location.
More information about the es-discuss