Adding unit test demonstrating failure of PostConstruction NotifyWhenAutowired for Context.
Implemented unsafe solution.

FIXME: There is a race condition in Autowire.
PROBLEM: If the desired context member is added between the FindByTypeRecursive and AddDeferred calls then the notification will not be satisfied.
Thread-correct (see file comments added in previous commit) NotifyWhenAutowired and Autowire methods.
Avoid missing type satisfaction due to simultaneous injection in to a parent context: FindByTypeRecursiveUnsafe makes calls while holding ALL necessary locks.
Merge pull request #77 from GabrielHare/bug-context-notify-posthoc

Bug context notify posthoc
Unit test demonstrates deadlock when nesting NotifyWhenAutowired.
Avoid deadlock from nested NotifyWhenAutowried calls by postponing satisfied call until after exit of FindByTypeRecursiveUnsafe.
Merge pull request #78 from GabrielHare/bug-nested-notify

Fix deadlock introduced when race conditions were avoided in context-notify-posthoc.
Ignore list updated
Fixing a CoreContext::Initiate reentrant deadlock

CoreRunnable::Start can potentially deadlock if it tries to start a subcontext; this behavior should be supported as there are cases where a subcontext should be initiated in response to parent initiation.
Merge pull request #80 from leapmotion/bug-reentrantinitiate

Fix CoreContext::Initiate reentrant deadlock
Merge branch 'develop' into feature-autoinit
AutoInit probably belong in PostConstructTest