Safety of concurrent_vector

Question

it is known that operator [] is not concurrently safe for writing: concurrent_vector::operator[] Operator But what if I guarantee that different threads will write to different vector positions. Like this (very much simplified example):

concurrent_vector<double> vec;
vec.resize(100);

parallel_for(0, 100, [&] (double ind)
{
    vec[ind] = ind*ind;
}

Is it concurrently safe or not? And if 'not' then why?

Thanks

_That_ would be safe even with regular old `std::vector<>`. What problem are you experiencing to prompt this question? — ildjarn, Mar 19 '12 at 21:08

score 2 · Accepted Answer · answered Mar 19 '12 at 21:10

2

Yes, it is concurrently safe as it's like if you are accessing different variables.

As ildjam pointed out in the comment that would be safe even with regular std::vector or, let me add, with simple arrays.

answered Mar 19 '12 at 21:10

Manlio

10,768
9
50
79

Thank you, guys.
I just wanted to check either I understand it right way. – IgorStack Mar 19 '12 at 21:34

Safety of concurrent_vector

1 Answers1