Jerome Gravel-Niquet

Definitely need to work that improvement in the default theme.

OT: It's a good crate! It's been working pretty great for me. Thanks for the hard work on it :) Oh maybe multiple contexts is a common thing. I'm assuming...

Oh, yes, that's the one! I didn't know how that kind of mutex was called.

Implemented this locally. Seems to help, but I'm not sure how to handle all the `Context::from_raw` which essentially would require me to make a new `ReentrantMutex` (because I'm storing it...

I'm currently testing this with a tokio multi-threaded event loop. I made a setTimeout native function that uses it. I added a lazy_static hash map like: ```rust lazy_static! { static...

> In your case, the mutexts only lock the thread during the execution of enter (i.e it's released and dropped as soon as the enter function is finished), therefore another...

> Sorry for being a bit vague No worries, you weren't. I have a specific use-case in mind that uses multiple runtimes and a single context per runtime. A multi-threaded...

From Gitter: https://gitter.im/Microsoft/ChakraCore?at=5b757c64a6af14730b433141 TL;DR: only 1 context can be active per thread at any given time, regardless of which runtime it belongs to. This means we'd need to share a...

I'm not sure the Runtime matters here. Looks like it's only a Context thing. Brain dump: - We don't need to track which context is active on the current thread...

I fixed the issue for my own use case. Using tokio 0.1.8 (just released). For every runtime: - I spawn a new thread that runs a tokio with the `CurrentThread`...