> Unfortunately, it precludes types from taking dependencies on their own address, It does not! You just have to make it non-copyable and non-moveable. std::mu

> Unfortunately, it precludes types from taking dependencies on their own address, It does not! You just have to make it non-copyable and non-moveable. std::mutex and std::atomic do exactly this. > As far as I know, there is no way to actually force a C++ class to be heap allocated. I’ve tried. As others have already pointed out: private constructor + factory method. However, this pattern is typically used for different reasons (implementation hiding or runtime polymorphism) and heap allocation is only a side effect. > This decays to heap allocation. No! The object might just as well live on the stack or have static storage duration.