leapmotion/autowiring — pull request #55 by codemercenary (2014-08-16 04:09:31+00:00)
Title: Updating atomic object to make use of a lock heirarchy scheme

Required because not all of our target platforms have std::lock (yet!)

For now we'll enforce a locking heirarchy with a simple predicate based on the assignee location in memory. This is guaranteed not to cause deadlocks as long as the copy operation is trivial or, at a minimum, doesn't attempt to obtain any locks.