Swift Around the Web
Whoa, I must not be using Protocols enough in Swift - I definitely didn't realize that you can't make optional protocol methods (especially since I'm used to seeing the optional keyword when working with UITableViewDataSource and UITableViewDelegate documentation). @ashfurrow's solution to this problem is to separate out the optional methods into their own protocols, which seems clean. Of course, the key is to re-evaluate your code and goals altogether to come up with a better, Swiftier solution. Challenge accepted.
"An interesting aspect of Swift is that there's nothing in the language related to threading, and more specifically to mutexes/locks. Even Objective-C has @synchronized and atomic properties. Fortunately, most of the power is in the platform APIs which are easily used from Swift." Make sure to scroll down for comments on the topic from @clattner_llvm himself!
- What is ARC and how is it different from Garbage collection.
- Strong reference cycles.
- How to resolved strong reference cycles with weak and unowned references in Swift taking real life examples
- Some of the unobvious (at least for a beginner) causes of memory leaks.
- Prevention/Precautions while coding.
- Cure — Detecting the causes with help of instruments.