I have hit a speedbump in a project I am working on. Basically, I have an Arc<T> cloned object that gets (move) captured in a closure, and that closure gets moved to another thread with thread::spawn. The compiler complains that T needs to be 'static but I don't see why that is necessary, as Arc<T> …

Why is T 'static constrained when using Arc<T> and thread::spawn

sudison March 14, 2019, 8:54am 6

2 Likes

Topic		Replies	Views
Lifetime problem when spawning a thread with arc mutex help	3	829	August 13, 2021
Why does thread::spawn need static lifetime for generic bounds? help	8	24250	July 21, 2022
Callback in multithreaded code help	11	1073	May 1, 2020
Arc<T> requiring a lifetime for T. Why? help	6	951	January 3, 2023
[Solved] Lifetime for Arc + Mutex + Thread help	4	3008	June 28, 2019