On Thu, Jul 19, 2012 at 3:04 AM, jMerliN <[email protected]> wrote:
> So I can't get my head around why this happens (I haven't dug through > v8's code to try to figure it out either), but this is really > inconsistent to me with how v8 constructs hidden classes in general. > The following is running in Node.js v0.8.2 (V8 v3.11.10.12). > FWIW: v8's internal optimizations are internal implementation details, and any client code which optimizes specifically for them will, long term, require more maintenance and possibly have more bugs/regressions. It is, in general, poor practice for client code to assume that it knows ANYTHING with certainty about a 3rd-party library beyond what is documented in the library's API docs... errr... well, okay, that might be the problem right there. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
