This addresses part of #1 by asserting, at construction time, where the impl_type is complete, that the storage alignment is an integer multiple of the constructed type's alignment. This doesn't solve the problem of giving users the option to align at whatever boundary they wish, but at least it prevents one class of undefined behaviour at compile time.
This addresses part of #1 by asserting, at construction time, where the
impl_typeis complete, that the storage alignment is an integer multiple of the constructed type's alignment. This doesn't solve the problem of giving users the option to align at whatever boundary they wish, but at least it prevents one class of undefined behaviour at compile time.