On Sat, May 12, 2018 at 1:20 AM, Jérôme Gravel-Niquet wrote:
> Another fiber might call v8_with_ctx_scope() again before the first call to
> it is done. With the same context. When I added a mutex, the problem seemed
> fixed. I just want to make sure this is limitation: you can't enter the same
>
On May 11, 2018 at 4:36:12 PM, Ben Noordhuis (i...@bnoordhuis.nl) wrote:
On Fri, May 11, 2018 at 10:05 PM, wrote:
> Yea, that makes sense. They do match up, but the function I use to get the
> context handle may be called more than once at the same time. I mean, the
> same context may be entered
On Fri, May 11, 2018 at 10:05 PM, wrote:
> Yea, that makes sense. They do match up, but the function I use to get the
> context handle may be called more than once at the same time. I mean, the
> same context may be entered multiple times concurrently and exited at
> different times. As soon as i
On Friday, May 11, 2018 at 2:45:06 PM UTC-4, Ben Noordhuis wrote:
>
> On Fri, May 11, 2018 at 7:36 PM, > wrote:
> > I've been wondering if it's possible to concurrently use v8::Locker.
> >
> > I'm binding to v8 from a single-threaded language that uses fibers for
> > concurrency (Crystal.) S
On Fri, May 11, 2018 at 7:36 PM, wrote:
> I've been wondering if it's possible to concurrently use v8::Locker.
>
> I'm binding to v8 from a single-threaded language that uses fibers for
> concurrency (Crystal.) Since it's a single thread, v8::Locker is always
> instantly available.
>
> This seems
