preventExtensions trap and its true/false protocol

2013-03-31 Thread David Bruant
Hi, The current proxy_spec [1], for the Object.preventExtensions built-in, suggests to read the result of the preventExtensions trap as a boolean and throw if falsy. From the developer perspective, this doesn't really add anything since it's already possible to throw from within the trap (and

Re: preventExtensions trap and its true/false protocol

2013-03-31 Thread Jeff Walden
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

Re: endianness (was: Observability of NaN distinctions — is this a concern?)

2013-03-31 Thread Vladimir Vukicevic
(Apologies for breaking threading -- subscribed too late to have original message to reply to.) David Herman wrote: On Mar 27, 2013, at 6:51 AM, Andreas Rossberg rossberg at google.com https://mail.mozilla.org/listinfo/es-discuss wrote: / There actually are (third-party) projects // with

Re: endianness (was: Observability of NaN distinctions — is this a concern?)

2013-03-31 Thread Kevin Gadd
One could also argue that people using typed arrays to alias and munge individual values should be using DataView instead. If it performs poorly, that can hopefully be addressed in the JS runtimes (the way it's specified doesn't seem to prevent it from being efficient). -kg On Sun, Mar 31, 2013

Re: preventExtensions trap and its true/false protocol

2013-03-31 Thread David Bruant
Le 31/03/2013 21:17, Jeff Walden a écrit : 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