From 50824b4e5c67fe1dbb014272d6ed809f629c3179 Mon Sep 17 00:00:00 2001 From: Mike Bierlee Date: Thu, 10 Jul 2014 01:12:02 +0200 Subject: [PATCH] Remove known, unsolvable, issue Any logical solution would endlessly autowire new instances if no stop condition is given. The current circular dependency resolution system provides such a stop condition just fine. --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 73c2608..2ff3a5f 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,6 @@ Poodinis can autowire circular dependencies when they are registered with single Known issues ------------ -* Due to preventive measures of recursion issues in circular dependencies, registrations which are supposed to yield new instances will not autowire classes for which a circular dependency is detected. A new instance will be resolved but the instance's members will not be autowired. * Resolving a class registered by supertype or interface will only autowire the members inherited from its supertypes and in the case of interfaces none at all. A workaround for this issue is to autowire members in the constructor of a class: ```d import poodinis.autowire;