News for hackers. Stuff that matters.

A comment on On Apple's Love Affair with Swift. Parent comment

Re:On Apple's Love Affair with Swift by gurkendoktor on Sunday August 12, 2018 @05:33AM (#17743665)
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?
[ Parent | on HN ]
Re:On Apple's Love Affair with Swift by jakobegger on Sunday August 12, 2018 @09:53AM (#17744347)
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.

[ Parent | on HN ]
Re:On Apple's Love Affair with Swift by lerno on Wednesday August 15, 2018 @05:42PM (#17770040)
No 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”.

[ Parent | on HN ]