4 ms·
Could you please give some concrete examples of how memory corruption has affected you in modern Objective-C? NSArray has range checks, delegates can't dangle a
by gurkendoktor 8y ago
Could you please give some concrete examples of how memory corruption has affected you in modern Objective-C? NSArray has range checks, delegates can't dangle anymore because they're weak references now. I think that leaves interaction with C APIs, but don't Swift users have to deal with UnsafeMutablePointer to use them - which isn't memory safe either?
- jakobegger 8y agoThe 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”.