Search Results
7/18/2025, 12:24:43 AM
>>105941489
You are kind of dense, aren't you?
>but you're still not doing any work here on the underlying array
slice::fill is the work here. It fills chunk, which is a part of buffer. The buffer is the underlying array and it gets changed, look at the print.
>Also .fill() says it clones the passed element which isn't a copy?
It's a memset.
>Also why would I want the ID of the thread here? I want to edit the underlying array.
It's called an example. By each thread filling their own chunk of underlying array, this example shows that it is possible to "give each thread a section of each array to work on without incurring additional copies", which is what you asked about.
Jfk, how did you even found your way to /g/
You are kind of dense, aren't you?
>but you're still not doing any work here on the underlying array
slice::fill is the work here. It fills chunk, which is a part of buffer. The buffer is the underlying array and it gets changed, look at the print.
>Also .fill() says it clones the passed element which isn't a copy?
It's a memset.
>Also why would I want the ID of the thread here? I want to edit the underlying array.
It's called an example. By each thread filling their own chunk of underlying array, this example shows that it is possible to "give each thread a section of each array to work on without incurring additional copies", which is what you asked about.
Jfk, how did you even found your way to /g/
7/16/2025, 9:53:51 AM
>>531426531
His next line is calling you a jeet/retard
His next line is calling you a jeet/retard
Page 1