anthill-di

Rust ioc system

The library is for deep tree of dependencies

Advantages:

async constructors (parallel building)
runtime injection
runtime check dependency cycles
3 type life cycle (transient/singleton/scoped)
3 injection way (simple trait constructor, async/sync closure as constructor, instance)
extensible dependency injection logic

Deficiencies:

runtime check dependency cycles take some time for synchronize
async building take some time for synchronize

Warning

Library required Rust nightly for trait as interface (Unsize)

Basic concepts

The components source is DependencyContext

``` rust /* creating root DependencyContext */

fn () { let rootcontext = DependencyContext::new_root() } ```

There are several ways to register components

``` rust /* all way for component registration */

async fn () { //let rootcontext = DependencyContext::new_root()

// adds component, which implement Constructor trait
root_context.register_type::<SomeComponent>(DependencyLifeCycle::Transient).await.unwrap();

// adds component from closure
root_context.register_closure(|_| Ok(SomeComponent {}), DependencyLifeCycle::Transient).await.unwrap();

// adds component from async closure
root_context.register_async_closure(
    move |_: crate::DependencyContext| { async move { Ok(SomeComponent {}) }},
    DependencyLifeCycle::Transient
).await.unwrap();

// adds an existing component
root_context.register_instance(RwLock::new(instance)).await.unwrap();

} ```

Each type of component registration (except instance registration) takes 3 life times
Instance registration is always a Singleton

```rust /* Life times */

async fn () { //let rootcontext = DependencyContext::new_root()

// instance per call
root_context.register_type::<SomeComponent>(DependencyLifeCycle::Transient).await.unwrap();
// single instance
root_context.register_type::<SomeComponent>(DependencyLifeCycle::Singleton).await.unwrap();
// instance per scope
root_context.register_type::<SomeComponent>(DependencyLifeCycle::Scoped).await.unwrap();

}

```

To register a component through a type, you need to implement Constructor trait

``` rust /* Constructor implementation */

[async_trait]

impl Constructor for SomeComponent { async fn ctor(_: crate::DependencyContext) -> BuildDependencyResult { Ok( Self { } ) } } ```

Components are given a unique context when they are built
You can store the context in a struct field and get dependencies anywhere in the component
Nested (child) dependencies can be requested from the context

``` rust /* Resolve nested service */

[async_trait]

impl Constructor for SomeComponent { async fn ctor(ctx: crate::DependencyContext) -> BuildDependencyResult { Ok( Self { nestedservice1: ctx.resolve().await?, nestedservice2: ctx.resolve().await? } ) } } ```

Components context is the same as the root context, which means it can register dependencies

``` rust /* register new dependency */

[async_trait]

impl Constructor for SomeComponent { async fn ctor(ctx: crate::DependencyContext) -> BuildDependencyResult { ctx.registertype::(DependencyLifeCycle::Transient).await .maperr(|e| BuildDependencyError::AddDependencyError { err: e })?;

    Ok( Self {
        nested_service1: ctx.resolve::<SomeComponent2>().await?,
        nested_service2: ctx.resolve().await?
    } )
}

} ```

You can resolve the first (by TypeId) or all matching dependencies

``` rust /* dependency resolving way */

async fn () { //let rootcontext = DependencyContext::newroot() //rootcontext.register_type::(DependencyLifeCycle::Transient).await.unwrap();

// return first (by TypeId) component
let mut dependency = root_context.resolve::<SomeComponent>().await.unwrap();

// return all match as Vector<SomeComponent> (look at service mappings section)
let mut dependency_vector = root_context.resolve_collection::<Box<dyn SomeTrait>>().await.unwrap();

}

```

Each life time resolve in a different way

``` rust /* dependency resolving match */

async fn () { //let rootcontext = DependencyContext::newroot() //rootcontext.registertype::(DependencyLifeCycle::Transient).await.unwrap(); //rootcontext.registertype::(DependencyLifeCycle::Singleton).await.unwrap(); //rootcontext.register_type::(DependencyLifeCycle::Scoped).await.unwrap();

// resolve transient
let mut dependency = root_context.resolve::<SomeComponent1>().await.unwrap();

// resolve singleton
let mut dependency2 = root_context.resolve::<Arc<SomeComponent2>>().await.unwrap();

// resolve scoped
let mut dependency3 = root_context.resolve::<Weak<SomeComponent3>>().await.unwrap();

// To get a mutable singleton you need to register with RwLock/Lock
// Constructor trait implemented by default for tokio::sync::RwLock<T>, std::sync::RwLock<T>

} ```

You can map a component to a service
By default, only the component's mapping to itself is created
You are not limited in the number of mappings

``` rust /* component to service mapping */

async fn () { //let rootcontext = DependencyContext::new_root()

// mapping at creation time
root_context.register_type::<SomeComponent>(DependencyLifeCycle::Transient).await.unwrap()
    .map_as::<dyn SomeImplementedTrait1>().await.unwrap();

// map after creation
root_context.map_component::<SomeComponent, dyn SomeImplementedTrait2>().await.unwrap();

} ```

Service is resolved in Box\

``` rust /* scope resolving */

async fn () { //let rootcontext = DependencyContext::newroot() //rootcontext.registertype::(DependencyLifeCycle::Transient).await.unwrap() // .mapas::().await.unwrap();

let service = root_context.resolve::<Box<dyn SomeImplementedTrait>>().await.unwrap();

} ```

Scoped components live until all Arc of scope are removed
Child instance contain scope of parent

If the parent changes scope before the child instance is created, the child instance will be created with the new scope created by the parent

You can always create a new scope, or set an old one

``` rust /* Scope manipulation */

[async_trait]

impl Constructor for SomeComponent { async fn ctor(ctx: crate::DependencyContext) -> BuildDependencyResult { // take old scope, we can save it for using two scope let oldscope = ctx.getscope();

    //instance from old scope
    let instance1 = ctx.resolve::<SomeInstance>().await?;

    // return new scope after create
    let new_scope = ctx.set_empty_scope();

    //instance from new scope
    let instance2 = ctx.resolve::<SomeInstance>().await?;

    // set old scope
    ctx.set_scope(old_scope);

    //instance from old scope
    let instance3 = ctx.resolve::<SomeInstance>().await?;

    Ok( Self { } )
}

} ```

Global context verifies link of the requested dependencies and return error in case of a circular dependency
If the check is successful, all subsequent requests for this pair link will not check for cycling

You can debug inner state:

``` rust async fn () { let rootcontext = DependencyContext::newroot() rootcontext.registertype::(DependencyLifeCycle::Transient).await.unwrap() .mapas::().await.unwrap();

println!("{root_context:#?}");

}

```

Basic example

```rust use asynctrait::asynctrait;

use anthill_di::{ Constructor, types::BuildDependencyResult, DependencyContext, DependencyLifeCycle };

struct TransientDependency1 { pub d1: TransientDependency2, pub d2: TransientDependency2, }

[async_trait]

impl Constructor for TransientDependency1 { async fn ctor(ctx: DependencyContext) -> BuildDependencyResult { Ok(Self { d1: ctx.resolve().await?, d2: ctx.resolve().await?, }) } }

struct TransientDependency2 { pub str: String, }

[async_trait]

impl Constructor for TransientDependency2 { async fn ctor(: DependencyContext) -> BuildDependencyResult { Ok(Self { str: "test".tostring() }) } }

[tokio::main]

fn main() { let rootcontext = DependencyContext::newroot(); rootcontext.registertype::(DependencyLifeCycle::Transient).await.unwrap(); rootcontext.registertype::(DependencyLifeCycle::Transient).await.unwrap();

let dependency = root_context.resolve::<TransientDependency1>().await.unwrap();

assert_eq!(dependency.d1.str, "test".to_string());
assert_eq!(dependency.d2.str, "test".to_string());

} ```

More shared examples present in src/tests folder

Little architecture overview

Register dependency + how construct type + lifecycle automatically generate Component + LifecycleBuilder + fake Service as component to component
Register addition Service component to implemented trait (maby later something else like closure buildings)
Request dependency validate link -> take first Service (or collection in future) -> call LifecycleBuilder by TypeId from Service -> LifecycleBuilder build Component as CycledInstance (empty/with Arc/with Weak) -> call Service with CycledInstance -> return Service

Refs

crate.io