@danieldg while I love the idea of upstreaming this awesome tokio PulseAudio mainloop into libpulse_binding, would you be open to publishing a separate crate for others (like me!) to be able to depend on it and use it?

From my perspective - and correct me if I'm wrong @jnqnfe - this crate seems to be more of a 1:1 binding between PulseAudio's APIs rather than "a bunch of rust tools and integrations for PulseAudio". So to me, a separate crate makes sense for what is essentially "a tokio implementation of a PulseAudio mainloop".

TL;DR: I would love it if the libpulse-tokio crate added in this PR could be published to crates.io. Whether that's by upstreaming here, or by publishing it separately.

@acheronfail - I just published the current version of this branch. While it still has a few limitations, those can be fixed in future versions. I'd be open to adding the maintainers here to the crate if it was merged, so it could be maintained/released in lock-step.

I just published the current version of this branch.

On crates.io? I couldn't find it.

https://crates.io/crates/libpulse-tokio

Thank you, I don't know why neither crates.io nor lib.rs could find it :(