News for hackers. Stuff that matters.
Re:Why asynchronous Rust doesn't work by valenterry on Sunday November 14, 2021 @01:49AM (#29215800)
Well, without further ado that's true. But the callback could of course set a result type somewhere (so, behave similar to a future/promise) and then we could know if/when it is finished and if it was successfully, or if it's still running (or broke without an error). But that's not Rust specific, that's just plain language-independent logic no?
Re:Why asynchronous Rust doesn't work by xondono on Sunday November 14, 2021 @05:12AM (#29216369)
> But the callback could of course set a result type somewhere [..] then we could know if/when it is finished

That would be a Mutex<>, the author mentions it in the comments. This would solve the “writing at the same time issue”, but not the lifetimes, so you’d need another change.

Instead of trying the mess of implementing special closures, you could just make your db static.