On Thu, Jul 30, 2020 at 8:21 PM Adrienne Walker wrote:
> Is there any way to know from a v8::Value whether serializing it will have
> side effects (at all or on particular properties)?
Apart from checking whether it's primitive (v->IsNullOrUndefined() ||
v->IsBoolean() || ...), I believe the ans
After trying and failing to generate a small repro (I always got soft
deopts instead of the bug), I realized that it's because Leszek already
fixed it! https://chromium-review.googlesource.com/c/v8/v8/+/2150586
On Wednesday, July 29, 2020 at 4:23:56 PM UTC-7, Seth Brenith wrote:
>
> A few brief
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
Hi Ben,
the Status before evaluate is "kInstantiated" and after "kErrored",
"--harmony_top_level_await" is not used.
I didn't check for the kErrored before, so I will just do that to get the
old behaviour.
Thanks for the hint!
Am Mittwoch, 29. Juli 2020 12:41:06 UTC+2 schrieb Ben Noordhuis:
>