Ivan Molodetskikh

> wcrs should be natively async There should still be a blocking sync API though for use-cases which are simple enough to not need the full async stack (like wl-copy,...

> `thread::block_on()` I like the idea, but that still requires bringing in an entire async crate to use wcrs which is undesirable if you don't use async elsewhere.

Another thing I want to consider is if it's possible to export a simple C API for copying and pasting so that wcrs could be used as a library from...

Oh yeah, yet another point to consider: wl-copy needs to be able to fork-and-not-exec to support the foreground mode (does it? Can we achieve the same behavior by doing a...

> You can [ask them](https://docs.rs/tokio/0.2.1/tokio/runtime/struct.Builder.html#method.num_threads) to use only one thread. That reads to me like it's still gonna spawn at least one thread on the pool.

Let me write down some goals of a new API. 1. Many toolkits offer multiple formats when copying e.g. images: you get `image/png`, `image/jpeg`, and so on and so forth....

Thanks for the detailed report! I think I need to finish updating to the newest wayland-rs before I investigate this. I should have most of the update done in the...

I've updated `wayland-rs`, do you mind re-testing on latest master in case it was an old `wayland-rs` issue?

I investigated, looks like it's https://github.com/Smithay/wayland-rs/issues/235 again. Using the `native_lib` feature makes the issue go away.

Upon bringing it up with the wayland-rs maintainer, looks like the issue isn't that, but runs a bit deeper: https://github.com/Smithay/wayland-rs/issues/376