On 2014/02/04 15:40:58, sof wrote:
https://codereview.chromium.org/118553003/diff/400001/src/symbol.js
File src/symbol.js (right):
https://codereview.chromium.org/118553003/diff/400001/src/symbol.js#newcode59
src/symbol.js:59: throw MakeTypeError('symbol_to_value', []);
On 2014/02/04 15:16:25, rossberg wrote:
> We should leave this out for now (and also not do it in toString). I
consider
> this a spec bug, since it seems inconsistent with the rest of the
language.
It
> also breaks our optimisation of not wrapping primitives, as you seem to
have
> observed (unless we move this file to sloppy mode).
Not just non-strict, but the methods would also have to be marked as
non-native.
Hm, why?
What has changed here since e.g.,
https://mail.mozilla.org/pipermail/es-discuss/2013-October/033876.html
Well, Allen does not mention throwing on unwrapped symbols there -- which
is why
I actually was somewhat surprised to see it in the spec.
Defining away what was the main part of this CL, is a suboptimal situation
(for
me.) But OK.
Sorry about that. :(
https://codereview.chromium.org/118553003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
