Rafael Bachmann

> Are you suggesting splitting this trait into a separate crate? What would be the hypothetical benefit of that? Modularity? Not the trait, I think, the "trait" being something like...

@1Dragoon you could do this: check out what `#[tokio::main]` actually does, it just creates a runtime and then launches it. You could do this yourself in a function that is...

@1Dragoon here's an example of how you could do it: https://github.com/barafael/achat/blob/27a91729abd42216bfadc44a4a9dcab4c1ce732b/bin/dump_client_gui.rs#L7 Notably, you can ```rust klask::run_derived::(Settings::default(), |args| { // This is roughly what `#[tokio::main]` does: tokio::runtime::Builder::new_current_thread() .enable_all() .build() .unwrap() .block_on(async...

I suppose this may be closed. @MichalGniadek what do you think?

Draft status since I'm still fixing some depreciation warnings.

Interesting, do you know if this is a bug or a feature in `clap`? I couldn't find any issue about it, might be worth opening one.

I can't reproduce the depreciation warnings anymore. I think they were fixed in 26f69831617c67cf6bd1928a032348915d9ebf19

The same problem haunts a number of other crates. It is tracked in clippy here: https://github.com/rust-lang/rust-clippy/issues/6902

The issue is being worked on in a generic way at: https://github.com/rust-lang/rust-clippy/issues/6902 As the faulty lint has now made it beyond nursery. Perhaps we can wait with merging this until...

Hey @reynoldsbd, Good point, thanks for letting me know about that. However, I could not get it to 'make' with the ".S" externsion... Could you post how you did it?