 /**
 Driving engine of the message passing through the app, with no need for Delegate pattern nor Singletons.
 
-Coordinable will piggy-back on the UIResponder.next? in order to pass the message through UIView/UIVC hierarchy of any depth and complexity.
+It piggy-backs on the UIResponder.next? in order to pass the message through UIView/UIVC hierarchy of any depth and complexity.
 However, it does not interfere with the regular UIResponder functionality.
 
 At the UIViewController level (see below), it‘s intercepted to switch up to the coordinator, if the UIVC has one.

	private struct AssociatedKeys {
		static var ParentCoordinator = "ParentCoordinator"
	}
	///	*Must* be set for View Controller acting as Coordinator.rootViewController
	public var parentCoordinator: Any? {
		get {
			return objc_getAssociatedObject(self, &AssociatedKeys.ParentCoordinator)
		}
		set {
			objc_setAssociatedObject(self, &AssociatedKeys.ParentCoordinator, newValue, .OBJC_ASSOCIATION_RETAIN)



extension UIViewController {
	/**
	Returns `parentCoordinator` if the current UIViewController has one,
	or its view's `superview` if it doesn‘t.

	---
	(Attention: from UIResponder.next documentation)

	The UIResponder class does not store or set the next responder automatically,
	instead returning nil by default.

