On Fri, Aug 26, 2022 at 11:32 AM Alex Kodat
wrote:
> Thanks Shu,
>
> Interesting. I always thought of the C++ API as fairly complete but maybe
> I just always happened to use the bits that are there. Of course I could
> create a script that contains functions that C++ can call to create and
> upd
Thanks Shu,
Interesting. I always thought of the C++ API as fairly complete but maybe I
just always happened to use the bits that are there. Of course I could
create a script that contains functions that C++ can call to create and
update a WeakMap (no real use for a WeakSet, at the moment), it'
Hi Alex,
There is no WeakMap and WeakSet support in API. The V8 API doesn't expose
many standard library JS values and objects. At least currently, there are
no immediate plans to expose them. More exposed surface means higher
maintenance burden going forward, so we're likely to consider exposing
Oh, single-threaded. I would have expected v8 to use a mutex around their
persistent (global handle) management. I'll try a mutex on my side and see
if that resolves the issue. Thanks for your help. 🤞
On Fri, Aug 26, 2022 at 12:52 AM dinf...@chromium.org
wrote:
> Hi,
>
> Those persistent/glo
That makes sense.
Thank you for your answer.
On Friday, August 26, 2022 at 1:58:37 AM UTC-7 Jakob Kummerow wrote:
> No, some Turbofan passes cannot be disabled, because they are required.
> SimplifiedLowering is a great example -- it changes ("lowers") the graph to
> the format that subsequent
Is there a way to create and manipulate WeakMaps and WeakSets from C++?
This seems like such an obvious missing piece in the C++ API that I'm sure
the answer will be embarrassingly obvious (apologies in advance).
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/gr
No, some Turbofan passes cannot be disabled, because they are required.
SimplifiedLowering is a great example -- it changes ("lowers") the graph to
the format that subsequent passes require.
On Fri, Aug 26, 2022 at 4:18 AM TL wrote:
> I am curious whether there are any options for the 'd8' to d
Hi,
Those persistent/global handles are single-threaded only, could it be that
you allocate such handles from multiple threads?
There is also v8::Global which Reset()s itself in the destructor
automatically. We would even like to remove v8::Persistent entirely at some
point
(see
https://bugs
