pre-RFC, JoinHandle::try_join()

Nokel81 · August 1, 2018, 4:52pm

I came across this while writing some tests and believe that it is also useful for software engineering outside of tests.

Currently, when a new thread is spawned, it returns a JoinHandle with which you can get the thread handle or join (wait for it to run to completion). What I am suggesting is the ability to test if a thread has finished or not.

It would have the following signature: pub fn try_join(self) -> Option<Result<T>>. I think that this would be useful for work sharing or even monitoring since you can get some information about the thread without blocking yours. (kill if it is running to long but still do work in the meantime).

cuviper · August 1, 2018, 5:30pm

Can that be implemented portably? On Linux with glibc, I know of pthread_tryjoin_np, but that np indicates that this is non-Posix. I don’t know about the other unix-ish targets, let alone Windows and others.

cuviper · August 1, 2018, 6:14pm

I found https://crates.io/crates/thread_tryjoin

It does use pthread_tryjoin_np, so this only works on Linux, but both linux-gnu and linux-musl should be fine. That crate is not trying to decode it into an Option as you suggest, so you’d have to interpret the EBUSY error yourself.

retep998 · August 15, 2018, 9:07pm

try_join would be trivial on Windows. Just change the timeout to 0, or even some number if you want a join_timeout.

github.com

rust-lang/rust/blob/d679b57a3a234a75926f1ffc5fe088c7ad97daf0/src/libstd/sys/windows/thread.rs#L70




pub fn set_name(name: &CStr) {
    if let Ok(utf8) = name.to_str() {
        if let Ok(utf16) = to_u16s(utf8) {
            unsafe { c::SetThreadDescription(c::GetCurrentThread(), utf16.as_ptr()); };
        };
    };
}


pub fn join(self) {
    let rc = unsafe { c::WaitForSingleObject(self.handle.raw(), c::INFINITE) };
    if rc == c::WAIT_FAILED {
        panic!("failed to join on thread: {}",
               io::Error::last_os_error());
    }
}


pub fn yield_now() {
    // This function will return 0 if there are no other threads to execute,
    // but this also means that the yield was useless so this isn't really a
    // case that needs to be worried about.

system · March 25, 2019, 8:30am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Join threads on drop libs	5	562	May 7, 2024
Design rationale: why uncaught panics in threads don't abort? language design	24	3806	December 24, 2020
Should JoinHandle<T> (from std::thread) implement Future?	4	2063	November 17, 2019
Joining and cooperative interruptible threads, for Rust? libs	6	1954	November 30, 2019
Thread::cancel() support libs	15	15474	March 25, 2019

pre-RFC, JoinHandle::try_join()

Related Topics