Re: [v8-users] How to wrap c++ obj during initialization and unwrap during binded function callback ??

Thanks for your reply Ben, I have tried as you suggested : context->Global()->SetInternalField(0, obj); but didn't worked ... am I doing anything wrong during the initialization ? On Monday, August 19, 2019 at 11:30:57 PM UTC+5:30, Ben Noordhuis wrote: > > On Mon, Aug 19, 2019 at

Re: [v8-users] How to wrap c++ obj during initialization and unwrap during binded function callback ??

Thanks your reply Ben, I have tried as you suggested : context->Global()->SetInternalField(0, obj); but didn't worked ... do i am doing anything wrong during the initialization ? On Monday, August 19, 2019 at 11:30:57 PM UTC+5:30, Ben Noordhuis wrote: > > On Mon, Aug 19, 2019 at

Re: [v8-users] Does v8 preserve locality of objects that were pushed from new space to old space?

There is no guarantee that locality will be preserved. It depends on where there is available space in old-space. You might get lucky :-) (This is well known to be one of the drawbacks of generational moving GCs, but as far as I'm aware our experiments indicate that the benefits more than make up

[v8-users] Does v8 preserve locality of objects that were pushed from new space to old space?

Does v8 preserve locality of objects that were pushed from new space to old space? Let's say I've created some objects within a loop so these objects will be stored in memory side by side because v8 uses bump pointer allocation for objects in new space. So far so good. After some time and some