On 2011/08/03 15:36:15, SkyLined wrote:
Actually, why is this an ASSERT? Should it not be a CHECK, so that it gets
compiled into non-debug builds?
It's important to not do the check in the set itself in release builds,
because
in loops this call can be performance sensitive. The caller (C++ code in the
runtime) needs to guarantee that it will not exceed the array bounds, and
this
is always the case unless there is a bug in the runtime code.
http://codereview.chromium.org/7564010/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
