On 2015/01/19 17:42:26, Toon Verwaest wrote:
I'm not sure what you are asking exactly. The previous error was most of
the
time "undefined is not a function". Now we match what Firefox does.
I'm saying a few things:
1. having `(intermediate value).` in the message looks kind of confusing,
I'm
not sure this would be more helpful for web developers (this might not
actually
be in the produced error message, but that's what it looks like from the
tests)
2. It would be really nice if the identifier / properties where the call
occurred was deserialized and included in the message (ie, "a.b (<<type>>
<<pretty value>>) is not a function"more informative than "<<pretty value>>
is
not a function". It would be nice
https://codereview.chromium.org/861623002/
--
--
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/d/optout.
