Hi- Is there any way to know from a v8::Value whether serializing it will have side effects (at all or on particular properties)?
Context: I was investigating indexeddb write performance in Chrome and discovered that when using inline keys, values are serialized and then immediately deserialized again to get the key value(s) out. This is because serialization might have side effects, so it's not safe to access the key from the original value. This takes quite a bit of time, especially on larger or more complicated values. I was wondering if there was anything that exists (and I just can't see from reading the code) or that we could add to make the calling code smarter about this. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/CA%2B1_fV_sm9vVbE34dfS%3Dp2CVy9mB7GJ4XkLsUMouVDjuBeB5NA%40mail.gmail.com.
