I am a threading noob and I am trying to write a custom thread safe generic list class in C# (.NET 3.5 SP1). I’ve read Why are thread safe collections so hard?. After reviewing the requirements of the class I think I only need to safely add to the list and return the list. The example shows pretty much all I want except it lacks the return list method therefore I’ve written my own public method like below:
Update: based on suggestions given I’ve reviewed my requirements and therefore simplified the class to as below:
public sealed class ThreadSafeList<T>
{
private readonly IList<T> list = new List<T>();
private readonly object lockable = new object();
public void Add(T t)
{
lock (lockable)
{
list.Add(t);
}
}
public IList<T> GetSnapshot()
{
IList<T> result;
lock (lockable)
{
result = new List<T>(list);
}
return result;
}
}
Agree with @jrista. There’s a semantics issue you need to resolve, and why is it called
Translate()? What is the intent?A – current code – return a read-only wrapper of the internal list
You still have threading issues if the original list is changed if another thread is iterating over the list. As long as you’re aware of this, it isn’t a huge issue.
B – a read-only copy.
This list has no threading issues because nothing modifies the new list. The only reference held is by the
ReadOnlyCollection<T>wrapper.C – a normal (writable) copy
Returns a new list, and the caller can do what they wish to their list without affecting the original list, and changes to the original list do not affect this list.
Does it matter if another consumer grabs a copy of the list and then modifies their copy? Do consumers need to see changes to the list? Do you just need a thread-safe enumerator?