Update memory barrier documentation (WOCommon, dfbe816)

Replace existing Doxygen comments with much clearer, more rigorous explanation of memory barriers and how they work, along with an example demonstrating the double-checked locking pattern for singletons.

Signed-off-by: Greg Hurrell <greg@hurrell.net>

← Revert "Remove methods which are no-ops under Garbage Collection" (WOCommon, 303c463)
Update Xcode project for latest version of Xcode (WOCommon, 9b40995) →

All snippets