Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't use tokio feature if a transient depends on accesskit with default-features #515

Open
lunixbochs opened this issue Feb 10, 2025 · 0 comments

Comments

@lunixbochs
Copy link
Contributor

lunixbochs commented Feb 10, 2025

8f937ba makes default-features incompatible with the tokio feature
Talon depends on zbus with the tokio feature, so it needs to depend on accesskit with the tokio feature
Talon depends on egui
egui depends on accesskit with default-features (egui shouldn't need to decide about accesskit_unix's executor anyway)

Talon -> egui -> accesskit (default-features=true) enables the async-io accesskit feature
Talon -> accesskit (features=[tokio]) enables the tokio feature

accesskit now denies this:

error: Both "async-io" (default) and "tokio" features cannot be enabled at the same time.

this kind of defeats the purpose of the tokio feature in accesskit imo, as I shouldn't be expected to patch egui for default-features = false to use it


anyway, at this point I think nobody should use the zbus/tokio feature in a library crate, and we should instead use this approach for tokio support when the tokio feature is enabled in accesskit_unix

here's the commit where I did it for ksni: talonvoice/ksni@15e31db

for now I'm turning off accesskit/tokio, and I wouldn't mind turning it back on with the zbus tokio feature removed like in the ksni change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant