>>105941341
>Concurrently working on arrays where you have to give each thread a section of each array to work on without incurring additional copies
Pic related.

>As far as I can tell even something as simple as doing vector math without copies requires jumping through a bunch of hoops
impl Vector {
fn add_assign(&mut self, other: &Vector) {
self.x += other.x;
self.y += other.y;
self.z += other.z;
}
}


>In C you can just spin up a thread and have it work on the section you hand it while other threads work on sections and have it updated in place. In Rust you have to prove those threads can't overlap thus requiring extra copies or moving parts of the array in and out of the original data structure/doing the work sequentially/using a third party library to do it for you.
Pic related.

>t always needs a copy or some sort of wrapping in a smart pointer which means I might as well use Go, have a better garbage collector than basic bitch reference counting and get access to green threads.
Pic related.

>>105613941
>In Rust this is impossible