LGTM!

I wonder if we should have something more drastic then ASSERT, since in case the
HandleScope API is not used correctly, as was in the test before, in release
build it'll try to use deallocated Isolate and not always fail... Maybe
API_Fatal or make HandleScope::Leave a noop if the underlying Isolate was
released?

http://codereview.chromium.org/3545004/show

--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev

Reply via email to