Hacker News new | ask | show | jobs
by chrisdevereux 4453 days ago
Lazily instantiating a shared object is the obvious reason. Doesn't need to be mutable.
1 comments

dispatch_once(3)[0] can be used for lazy initialization without concern for the calling class and without synchronizing on a shared object. This is (likely) cheaper in most cases then entering a @synchronized block.

0 - https://developer.apple.com/library/mac/documentation/Darwin...

Yes. In general, either GCD or lower level atomic ops are a better choice for thread-safety than @synchronized blocks. Just pointing out that there are reasons other than global mutable state for wanting a critical section in a class method.