Consider the following move-only type: struct MoveOnly { MoveOnly() = default; ~MoveOnly() = default; MoveOnly(const MoveOnly&) = delete; MoveOnly& operator=(const MoveOnly&) = del...

The following code prints whether std::atomic<bool> is trivially copyable: #include <atomic> #include <iostream> #include <type_traits> int main(){ std::cout << std:...

Example code could be found below or on godbolt. Say we have 4 classes: S<T>: holding a data member. SCtor<T>: holding a data member and has a template constructor. SCtorMutable<T...

Code is like: #include <iostream> #include <type_traits> class A { A() = default; A(const A&) = default; A(A&&) = default; A& operator=(const A&) = defaul...

The standard says A trivially copyable class is a class: (1.1) that has at least one eligible copy constructor, move constructor, copy assignment operator, or move assignment operator ([special], ...

A class with all special functions defaulted except a non-trivial destructor is not trivially move or copy constructible. See https://godbolt.org/z/o83rPz for an example: #include <type_traits&g...

std::is_pod has been deprecated in C++20. What's the reason for this choice? What should I use in place of std::is_pod to know if a type is actually a POD?

With the introduction of c++11, trivially copyableness has gotten quite relevant. Most notably in the use of 'std::atomic'. The basics are quite simple. A class foo is trivially copyable if: foo* ...