…ouldn't be contained anymore
…me oddities in its API discovered during documentation writing
…diately after removing a mapping in Injector#unmap
…vent using the injector in Flash Player < 10.1
… the call to InjectionMapping#seal()
…ndency provider's class and creates a new instance of it with dependencies injected into for each call to DependencyProvider#apply, enabling custom providers with their own dependencies.
…o dispatched during Injector#injectInto, now.
…on: POST_INSTANTIATE, PRE_CONSTRUCT and POST_CONSTRUCT
…ing, including unmapping it in the injector.
… "rule" in the source and tests code
…e of mappingId-strings
…ion of removing InjectionPointConfig
…ector has a mapping for the request in question
…like child injectors and soft mappings and increasing performance by another ~25% With this change, all mappings to providers are stored in a dictionary per injector and updated by the InjectionRule on provider-change. The InjectionPointConfigs got an apply-method that iterates over the injectors until it finds a provider-mapping and then applies it directly, removing several levels of indirection from the process.
…s now have an optional "name" parameter again. This changed shaved off about 150 LOC and is preparation for vast changes to dependency resolution.
… performance improvement
…ed in Injector
…y and moved the only usage into the SingletonProvider's ctor, simplifying the DependencyProvider interface
…dencies are to be provided This change enables providing different values based on the class requesting a dependency. A major use-case is a logger that's pre-configured for the class it is used in.
…ced ConstructorInjectionPoint#createInstance and made NoParamsConstructorInjectionPoint inherit from that instead.
Specifically, turned array of injection points into a linked list and changed method (and ctor) parameter values gathering to reuse one array instance instead of creating and discarding a new instance for each injection.