== Quote from dsimcha ([email protected])'s article
> 8. The high-level, templated allocator functions now have a default
> implementation in terms of lower-level allocator functionality, provided
> by the TypedAllocatorMixin mixin in std.allocators.allocator. The idea
> is that an allocator may have better ways of accomplishing this stuff,
> but this mixin is usually a reasonable default and will avoid code
> duplication across allocators. I'm leery of including it in the
> DynamicAllocator interface, though, because for some allocators it's
> just plain wrong. For example, the default array() implementation just
> plain wouldn't work with RegionAllocator for huge ranges.
I just realized that the fact that this is mixed into RegionAllocator didn't
make
it into the DDoc anywhere. Is there any easy way to get DDoc to document that a
mixin template has been mixed into a class/struct? I.e.:
struct Foo {
/// Document that this is mixed in.
mixin SomeMixin;
}
