Crates.io | dill |
lib.rs | dill |
version | 0.9.3 |
source | src |
created_at | 2021-07-09 17:45:45.784074 |
updated_at | 2024-12-07 00:36:33.109015 |
description | Runtime depenency injection library. |
homepage | https://github.com/sergiimk/dill-rs |
repository | https://github.com/sergiimk/dill-rs |
max_upload_size | |
id | 420841 |
size | 43,738 |
This crate is still in early stages and needs a lot of work, BUT it's in active use in kamu-cli
- a fairly large project organized according to Onion/Clean Architecture. We are continuing to improve this crate as we go and encounter more sophisticated DI scenarios.
/////////////////////////////////////////
// Define interfaces in traits
trait A: Send + Sync {
fn test(&self) -> String;
}
// Implement traits to define components
#[component]
struct AImpl {
// Auto-inject dependencies (also supports by-value)
b: Arc<dyn B>,
}
impl A for AImpl {
fn test(&self) -> String {
format!("aimpl::{}", self.b.test())
}
}
/////////////////////////////////////////
trait B: Send + Sync {
fn test(&self) -> String;
}
#[component]
struct BImpl;
impl B for BImpl {
fn test(&self) -> String {
"bimpl".to_owned()
}
}
/////////////////////////////////////////
// Register interfaces and bind them to implementations
let cat = Catalog::builder()
.add::<AImpl>()
.bind::<dyn A, AImpl>()
.add::<BImpl>()
.bind::<dyn B, BImpl>()
.build();
// Get objects and have their deps satisfied automatically
let inst = cat.get::<OneOf<dyn A>>().unwrap();
assert_eq!(inst.test(), "aimpl::bimpl");
Injection specs:
OneOf
- expects a single implementation of a given interfaceAllOf
- returns a collection of all implementations on a given interfaceMaybe<Spec>
- Returns None
if inner Spec
cannot be resolvedComponent scopes:
Transient
(default) - a new instance is created for every invocationSingleton
- an instance is created upon first use and then reused for the rest of calls#[component]
macro can derive Builder
:
struct
or on impl
block with Impl::new()
functionArc<T>
, T: Clone
, &T
Option<T>
is interpreted as Maybe<OneOf<T>>
specVec<T>
is interpreted as AllOf<T>
specBuilder
#[interface]
attribute#[meta(...)]
attributePrebuilt / add by value support
By value injection of Clone
types
Catalog
can be self-injected
Chaining of Catalog
s allows adding values dynamically (e.g. in middleware chains like tower
)
The type implementor (and not type user) usually has the best knowledge of what the optimal lifecycle for the type should be and its concurrency characteristics, thus implementors should be in control of the defaults
stable
rustScope
s external to Builder
s so they could be overriddenArc
, Option
, Vec
to dependency specs instead of relying on macro magictrybuild
tests (see https://youtu.be/geovSK3wMB8?t=956)add_*
with generic add<B: Into<Builder>>
new()
Arc<dyn Iface>
can be hidden behind a movable object
This even further hides lifetime management from consumers
Allows generic methods to be implemented to improve usability of dyn Trait
(e.g. accepting impl AsRef<str>
parameters instead of &str
)