memory_management

Aedi, a dependency injection library.

Aedi is a dependency injection library. It does provide a set of containers that do IoC, and an interface to configure application components (structs, objects, etc.)

Aim:

The aim of library is to provide a dependency injection solution that is feature rich, easy to use, easy to learn, and easy to extend up to your needs.

D by default comes with garbage collector which is responsible for destruction and deallocation of components that were used, and discarded by the application. Current implementation of garbage collector can be inefficient for cases when many small objects are continously created and destroyed by application. Therefore aedi framework allows users to select what allocation strategy to use for managed components by using std.experimental.allocator library.

To change the allocator used for components in a container, it is possible to pass new allocator implementation to configure method as third argument just like in example below:

with (container.configure("singleton", Mallocator.instance.allocatorObject)) {
    // ... registered components with Mallocator as allocator for them
}

The allocator passed in configure will be used as default implementation. As alternative syntax it is possible to pass the allocator in a fluent syntax by chaining along to configure with allocator as it's argument. Example below shows such variant:

with (container.configure("prototype").along(MmapAllocator.instance.allocatorObject)) {
    // ... registered components with Mallocator as allocator for them
}

The default allocator strategy can be overriden per component by directly specifying the allocator that should be used by registered component using allocator property for registered component. Example below shows such use case:

1 register!Size("size.sedan") // Register a size of a generic "sedan" into container
2     .set!"width"(200UL)
3     .set!"height"(150UL)
4     .set!"length"(500UL)
5     .allocator(MmapAllocator.instance.allocatorObject); // Change allocator object for this particular component to mmap allocator.

As a consequence to using custom allocation strategies, for all containers, terminate method should be called when containers lifetime ends (whether at end of application, or during some other event), otherwise it is not guaranteed that components are finalized correctly, even if they were allocated on garbage collector.

Members

Classes

Car
class Car

A class representing a car.

CarManufacturer
class CarManufacturer

A manufacturer of cars.

DieselEngine
class DieselEngine

A concrete implementation of Engine that uses diesel for propelling.

ElectricEngine
class ElectricEngine

A concrete implementation of Engine that uses electricity for propelling.

GasolineEngine
class GasolineEngine

A concrete implementation of Engine that uses gasoline for propelling.

Tire
class Tire

Tire, what it can represent else?

Interfaces

Engine
interface Engine

Interface for engines.

Structs

Color
struct Color

A struct that should be managed by container.

Size
struct Size

Size of a car.

Meta

Authors

aermicioi

License

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.