@0d50376e this might be a bad question but as someone who finds async rust confusing and who (I think) has no real need to use it, do you think there's a reason for me to learn about async rust? 

i've been trying on and off for years to find a small subset of rust that I can actually get comfortable with and I haven't yet been able to figure out which parts of Rust I want to learn vs ignore 

 @e06c1f25 it's entirely possible to "avoid async rust as much as possible" if you're not writing primarily networked apps (or other kinds of apps that are asynchronous by nature). I should actually write a guide about that: if you don't really have performance constraints (most don't), it's really easy to pull off. 

 @0d50376e i'd love to read that article! when i talk about avoiding async rust i'm talking about programs that interact with networking (like for example a program that captures packets) but aren't very performance sensitive 

 @e06c1f25 yeah exactly! I mean that use case is really just "build a current_thread tokio executor from one of your threads and move a channel sender into it, then from the sync side use blocking_recv" (see https://docs.rs/tokio/latest/tokio/sync/mpsc/index.html#communicating-between-sync-and-async-code)

but yeah! 

 @0d50376e i did not understand any of those words but maybe if you write a post about it I will :)