C#•3y ago

✅ Would a ConcurrentDictionary be necessary if I am only adding and never removing?

Would a ConcurrentDictionary be necessary if I'm only ever adding keys and never removing them? Also I'm not using the values of the dictionary so if ConcurrentDictionary is not needed I could use a regular HashSet instead.

TeBeCo•7/17/23, 11:20 AM

anythign cross thread is crossthread

TeBeCo•7/17/23, 11:20 AM

regardless or the type of operation

TeBeCo•7/17/23, 11:20 AM

Adding mutate the collection

TeBeCo•7/17/23, 11:20 AM

removing also mutate the collection

TeBeCo•7/17/23, 11:20 AM

it doesn't matter if you stick to only and ever Add

TeBeCo•7/17/23, 11:21 AM

if you have MANY call to .Add.Add at the same time using a non-thread safe collection it's still non-thread safe

TeBeCo•7/17/23, 11:22 AM

the actual resolve of .Add.Add on a NORMAL Dictionary is that you MIGHT ends up with

null

null

value inserted becuase of a thread safety issuecode inside Dictionaru<T, U>Dictionaru<T, U>

TeBeCo•7/17/23, 11:22 AM

which is literally one of the issue ConcurrentDictionaryConcurrentDictionary address

nathanAjacobsOP•7/17/23, 11:26 AM

Thank you for your response. That totally makes sense

TeBeCo•7/17/23, 11:36 AM

on remove you could have even more funky thing

TeBeCo•7/17/23, 11:36 AM

it also could crash for both AFAIK

✅ Would a ConcurrentDictionary be necessary if I am only adding and never removing?

Similar Threads

Similar Threads

Similar Threads