Jiahao XU

Perhaps we can enable all features specified by `required-features` in `[[bin]]` and `[[test]]`?

Maybe consider using [dashmap]? It is designed to be a high-performance hash map designed for concurrency. I would say it actually fit quite well with caching. [dashmap]: https://crates.io/crates/dashmap

There’s also another crate [left_right] that also provides better concurrency than `RwLock`. It is designed to be make reading scale linearly and not blocked by writing while making the writing...

@jaemk Maybe `T: ‘static` can be used, which requires `T` to be either owned or contains only reference to`’static` data.

> Though I am doubtful that this would be possible; we'd have to generate some type for debuggable to resolve to which wouldn't be solvable except for maybe a trait...

> @NobodyXu That may require some experimentation, but my instinct tells me that `impl Trait` won't help us here. The reason why is that we can't guarantee that the existential...

> `match_type!` doesn't do any conditional compilation; it could be thought of it as being more similar to `if cfg!() {}` as opposed to `#[cfg()] {}`. All branches are present...

> I'm not sure even then would this help. The problem is that in Rust, traits are not considered types (unlike interfaces in many languages). So you can't actually "compare"...

Maybe make a fork of this library and contribute to the new library instead?

I have added cargo-binstall to https://github.com/taiki-e/install-action , which installs popular crates for rust CI from binary (including non-rust one). Though it is not the official one, there are people using...