The end of the video mentions trivial relocatability (around the 48th minute), saying that it means that a type allows objects being moved by memcpy-and-forget, and that the C++ committee is working to include that in the standard. If only that were so... The WG21, for reasons they are yet to articulate, adopted a definition of "trivial" relocatability that breaks this property, by saying that polymorphic types can be "trivially" relocated, which cannot happen just by memcpy, because when the polymorphic object is sliced, the copied vtable pointer is wrong. This either destroys or severely complicates many use cases for trivial relocatability.