Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The new namespace System.Collections.Concurrent contains concurrent collections for dictionary, queue and stack among other classes. Anyone know why is it that there is no ConcurrentList?
I’ve posted a new question explaining my current scenario. I preferred that to changing the whole sense of the original question. Here’s the link to the new question.
Random access doesn’t make much sense on a data structure that’s changed from another thread.
If you look at the concurrent collections, you’ll notice that their interface is specifically designed to work well with multi threaded access. I can’t think of a useful list-like interface that works well with multithreaded code.
Random multi threaded access can make sense if the elements are never moved, but then you have an array.