3 ms·
The easiest way to cause memory issues is to access mutable collections from multiple threads. I really wish NSMutableArray and friends were thread safe... Unf
by jakobegger 8y ago
The easiest way to cause memory issues is to access mutable collections from multiple threads. I really wish NSMutableArray and friends were thread safe...
Unfortunately, Swift doesn't fix that AFAIK.
- lerno 8y agoNo no no. That is a one-way trip to hell. There is no ”good for all threading scenarios” thread safe mutable array design. I’ve debugged too much java code where the programmers thought that ”thread-safe” meant ”no need to think about threading issues”.