Tatsuya Kawano

Started to use `AtomicCell` for wight based eviction: https://github.com/moka-rs/moka/pull/24/commits/4404e6fd1cca5d41aa59688b7b67c842425c7be3

Hi. Thanks for opening this pull request. `getrandom` is used by only one unit test. I am not sure what would be the best way to do this, but probably...

As for `getrandom`, perhaps the followings would work? ```toml [target.'cfg(not(target_arch = "wasm32"))'.dev-dependencies] getrandom = { version = "0.2" } [target.'cfg(target_arch = "wasm32")'.dev-dependencies] getrandom = { version = "0.2", features =...

Thanks for providing the details. > Keep in mind that `uuid/js` needs to be triggered for `wasm32` as well, so you do need to have a `js` feature for it...

> I am using `unsync` because `wasm32-unknown-unknown` (browser) doesn't have threads and `sync` just crashes in the builder, which is somewhat expected. That is what I thought. > I actually...

If you could create a tiny wasm project for me to play with moka on a web browser, that will be a great help. I will use it to figure...

> As for the threads part, you can make `sync::Cache` not to spawn background threads by doing _all_ the followings: > > * Call `CacheBuilder`'s `thread_pool_enabled` method with `false`. ([doc](https://docs.rs/moka/0.9.3/moka/sync/struct.CacheBuilder.html#method.thread_pool_enabled))...

> It would be great if the cache could simply tell me whether it was fresh or cached. Technically, this will be very easy to implement. `get_with` internally tracks whether...

Hi. Thank you for reporting the issue. Which OS and CPU architecture did you use? Perhaps Linux x86_64? And you used a multi-core machine, right? When moka cache is not...

A quick update: I am currently investigating why the system spent lots of time in Linux `futex_wait` while all worker threads in the thread pool were mostly sleeping. I created...