On 2013/09/10 08:56:29, loislo wrote:
On 2013/09/10 08:47:56, Yang wrote:
> Having the string content appear as name seems valuable. How about
setting a
> certain limit so that we stringify only strings with lengths below that
limit?
> That way, whether to show string content would not depend on the string
type.
we have had 1k limit for the strings but
it doesn't solve the problem because the cons string uses only 40 bytes.
So in our case we use 25 times more memory.
I will reconstruct and show the content of the cons and sliced strings on
DevTools front-end side.
Usually we show only 100 strings at a time. So it wouldn't be a
performance
issue.
I was rather thinking about the string length than the object length on the
heap. If we so far read the entire content of the string, it should be easy
to
read the string length first, right?
https://codereview.chromium.org/23460027/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
