Reputation
Next privilege 200 Rep.
See reduced ads
Badges
10
Newest
 Informed
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 45 votes cast
Apr
12
accepted What problems might arise if I didn't make a method static when I could?
Apr
11
comment What problems might arise if I didn't make a method static when I could?
yeah I upvoted both of you, but his is more thorough and useful to me
Apr
11
comment What problems might arise if I didn't make a method static when I could?
@BasileStarynkevitch you are right, I retagged
Apr
11
revised What problems might arise if I didn't make a method static when I could?
edited tags
Apr
11
comment What problems might arise if I didn't make a method static when I could?
@gnat the first is close but not really what I am asking, I am asking what the problems might be, the other is asking specifically on memory consumption
Apr
11
asked What problems might arise if I didn't make a method static when I could?
Feb
17
comment Should if/else statements be arranged by rareness of cases or difficulty of dealing with them?
why is it more readable? I see no difference between the two in terms of readability
Dec
4
awarded  Informed
Nov
18
awarded  Critic
Oct
26
awarded  Popular Question
Aug
27
accepted Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
Aug
25
comment Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
the copy is necessary as each reader will get the data and edit it in it's own way, and all readers must get the un-edited data
Aug
25
comment Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
all the "reader" threads copy the list locally to modify it. Are you suggesting that the writer also does copying to update the list? writes locally and then just locks to update?
Aug
25
comment Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
yes but from my experience locks are faster than memory barriers, I'm looking into waits to replace the traditional lock with something faster
Aug
25
comment Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
Order is important, so concurrent bag is out of the question. During the write operation I am also performing LinQ on the list. Also instead of using interlocked.exchange, Is it not the same if I write the data to a separate list and lock before updating the thread accessed one?
Aug
25
comment Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
edited my question with some clarifications
Aug
25
revised Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
added 772 characters in body
Aug
25
awarded  Editor
Aug
25
revised Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?
added 5 characters in body
Aug
25
asked Does ReaderWriterLockSlim provide thread safety and speed efficiency (compared to a traditional lock) when using a List?