NOT LGTM: I don't think that anything deoptimizer-related is really
performance-critical. (If we have benchmarks for this, I'd like too see
them.)
Furthermore, *if* we decide to improve this, we should really use
std::binary_search: Making DeoptimizationOutputData a ForwardIterator is
very
easy, much less error-prone than writing the n-th binary search by hand and
much
more readable and flexible.
https://codereview.chromium.org/334713011/
--
--
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.
