3 ms·
I wish that some of these folks complaining about how rust libraries force you to use async would go out and write some equivalent libraries with synchronous AP
by mplanchard 3y ago
I wish that some of these folks complaining about how rust libraries force you to use async would go out and write some equivalent libraries with synchronous APIs. Rust's philosophy has always been to let library authors explore a problem space before (if ever) pulling stuff into the stdlib, and I think it is generally only beneficial for the ecosystem to have multiple ways of solving a problem.
- insanitybit 3y agoI think it goes to show that the vast majority of Rust devs don't actually care about this problem, otherwise they'd be doing that already. Like, providing a sync API over an async API is almost always as simple as: struct SyncThing { async_version: AsyncThing } impl SyncThing { pub fn sync_api(&self) { block_on(self.async_version.sync_api) } } If this were really such a huge problem I think we'd see more PRs. I get that there's some survivorship bias here, but still...