I would say it's not true that concurrency means that things are executed sequentially.
Concurrency means that, and Wikipedia wors it really well: "... is the ability of different parts or units of a program, algorithm, or problem to be executed out-of-order or in partial order, without affecting the final outcome."
Importantly, it implies that these sliced up parts of a program can also be reordered, partly executed, continued and parallelized(!) at the system's will.
Go for example makes this very clear: Concurrency is concurrency whether or not the amount of OS threads is 1 or > 1.
Basically, one could say that if code is concurrent, it's a prerequisite of it being able to be paralellized.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would say it's not true that concurrency means that things are executed sequentially.
Concurrency means that, and Wikipedia wors it really well: "... is the ability of different parts or units of a program, algorithm, or problem to be executed out-of-order or in partial order, without affecting the final outcome."
Importantly, it implies that these sliced up parts of a program can also be reordered, partly executed, continued and parallelized(!) at the system's will.
Go for example makes this very clear: Concurrency is concurrency whether or not the amount of OS threads is 1 or > 1.
Basically, one could say that if code is concurrent, it's a prerequisite of it being able to be paralellized.