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.
This commit is contained in:
Mike Bierlee 2014-07-10 01:12:02 +02:00
parent 5caf57d31d
commit 50824b4e5c

View file

@ -123,7 +123,6 @@ Poodinis can autowire circular dependencies when they are registered with single
Known issues 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: * 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 ```d
import poodinis.autowire; import poodinis.autowire;