I was talking about special cases that can be optimized, but the uncommon use
case would be more of a code smell than anything else, `string + new
MyClass()`. I'm well aware of the common use of O.p.toString in type detection.
I mistook the {Number,String}.p.toString as part of O.p.toString. That was the
core of the ambiguity/stupidity on my part.
I would say that the JIT may be able to use branch prediction and get around
that problem to a large extent.
On a side note, it may become common and suggested practice to declare a
@@toStringTag for all exported classes.
--
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" 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.
