News for hackers. Stuff that matters.

A comment on Concurrency in Rust. Parent comment

Re:Concurrency in Rust by fndjdh on Sunday March 27, 2016 @05:23AM (#11369432)
You seem to have concurrency confused with parallelism. Concurrency just means working on another task before the prior one has completed. You're describing parallelism which is doing multiple tasks at the same time.
[ Parent | on HN ]
Re:Concurrency in Rust by m0th87 on Sunday March 27, 2016 @11:48AM (#11370341)
Parallelism necessarily implies concurrency [1]

So, "SIMD concurrency" is not incorrect (although SIMD parallelism is more correct :)

1: http://programmers.stackexchange.com/a/155110

[ Parent | on HN ]
Re:Concurrency in Rust by naasking on Sunday March 27, 2016 @12:53PM (#11370562)
This not true. CPUs have instruction parallelism, even on a single CPU, but there is no observable concurrency.

SIMD is data-level parallelism, not concurrency.

[ Parent | on HN ]
Re:Concurrency in Rust by z1mm32m4n on Sunday March 27, 2016 @01:15PM (#11370641)
By SIMD concurrency, I meant that I was curious about a construct that actually translated into simultaneously executing code, not just a construct that denotes work that "could" be done simultaneously.
[ Parent | on HN ]