It is recommended that threads support context transfer and automatically perform clone operations

[1057105012]

Code

fn main() {
    let (sx, rx) = mpsc::channel();
    let handle = thread::spawn(move |sx, rx| {
        sx.send("hello").unwrap();
    });
    handle.join().unwrap();
}

It is recommended that threads support context. As shown in the figure, the context automatically performs cloning operations, which can avoid code, like this let handle = thread::spawn(move |sx, rx| {} not sx.clone(), rx.clone()。　

This operation can be understood as opening an isolation domain. Or abstract it into a more general concept. Rust allows the creation of isolated domains. All external borrowing in the isolation domain is automatically recognized as a clone operation

[theemathas]

Something similar to this is a 2024H2 project goal.
https://rust-lang.github.io/rust-project-goals/2024h2/ergonomic-rc.html
rust-lang/rust-project-goals#107

[fmease]

I wonder if we should close this in favor of:

• Experiment with ergonomic ref-counting rust-project-goals#107
• Simplify lightweight clones, including into closures and async blocks rfcs#3680
• Add closure-move-bindings RFC rfcs#3512

[fmease]

Closing in favor of rust-lang/rust-project-goals#107