The Misconceptions of C++ Developers

In recent years since moving to C++ 11, there is a lot of misinformation about the broad topic of move semantics. Part of it is syntactic because an R-value reference has two ampersands and a universal reference which the standardization company now calls forwarding references also have two ampersand but they actually behave in quite different ways. And then there's just a lot of vocabulary confusion about, for example, what does it mean to be a copyable type? Does that mean it can be moved or what does it means to be a moveable type? Do that mean it could be copied? Because some types support copy semantics but don't support move semantics. If you apply,