[resending because v8-users rejects email from non-subscribers]
Right, you cannot tell in general whether something can be serialized
without side effects (though you can tell that certain things definitely
won't have side effects). And if the spec says the value should be
serialized (or content e
สวัสดี
ในวันที่ วันพฤหัสบดีที่ 6 สิงหาคม ค.ศ. 2020 เวลา 7 นาฬิกา 20 นาที 12 วินาที
UTC+7 ad...@chromium.org เขียนว่า:
> On Tue, Aug 4, 2020 at 1:32 PM Adrienne Walker wrote:
>
>> On Thu, Jul 30, 2020 at 9:57 PM Ben Noordhuis
>> wrote:
>>
>>> On Thu, Jul 30, 2020 at 8:21 PM Adrienne Walker
>
On Tue, Aug 4, 2020 at 1:32 PM Adrienne Walker wrote:
> On Thu, Jul 30, 2020 at 9:57 PM Ben Noordhuis wrote:
>
>> 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 pr
On Tue, Aug 4, 2020 at 10:32 PM Adrienne Walker wrote:
>
> On Thu, Jul 30, 2020 at 9:57 PM Ben Noordhuis wrote:
>>
>> 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
On Thu, Jul 30, 2020 at 9:57 PM Ben Noordhuis wrote:
> 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->IsN
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
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