Skip to content

Enable reuse of Injection Members #19

Description

@ENikS

Description

In current implementation each injected member is uniquely associated with a member and a registration.

Problem

Creating an unique injection member for each individual registration even when they could be reused (default constructor for example) creates unnecessary memory and performance overhead.

Solution

This could be solved by not storing selection information with the InjectionMember and do static selection during resolution.

Impact

Minimal, if any

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions