News for hackers. Stuff that matters.
Re:Why asynchronous Rust doesn't work by valand on Wednesday March 10, 2021 @03:02AM (#26408947)
`

    fn do_work_and_then(func: fn(i32)) {
        thread::spawn(move || {
            // Figuring out the meaning of life...
            thread::sleep_ms(1000); // gee, this takes time to do...
            // ah, that's it!
            let result: i32 = 42;
            // let's call the `func` and tell it the good news...
            func(result)
        });
    }
`

you missed a snippet, a thread is spawned.

edit: formatting

Re:Why asynchronous Rust doesn't work by imtringued on Wednesday March 10, 2021 @04:38AM (#26409517)
If for some magic reason thread::sleep_ms(1000) takes longer than 2000ms the main function would reach its end and deallocate the closure that is about to get called. Basically use after free.
Re:Why asynchronous Rust doesn't work by richardwhiuk on Wednesday March 10, 2021 @06:41AM (#26410228)
And that's possible, because the sleep call is a suggestion, not a guarantee. If the CPU is blocked for 2s, then the order of waking the threads is undetermined, and the race will occur.
Re:Why asynchronous Rust doesn't work by mav3rick on Wednesday March 10, 2021 @11:49AM (#26413248)
That is technically a race (sure) but at that point the program is getting killed anyway. Agree on the overall point though. I am a big fan of moving complete ownership / lifetime. It just makes things easier to reason about. In Chromium weak pointers are used to solve this use after free problem.