Does a copy constructor/operator/function need to make clear which copy variant it implements?

Question

Yesterday I asked a question about copying objects in C#, and most answers focussed on the difference between deep copy and shallow copy, and the fact that it

Answer 1

Most C++ programmers do not use the terms "shallow copy" and "deep copy" for the very good reason that there is only normally one way to copy an object. This is particularly true in C++ because the compiler uses the copy constructor in many situations where the programmer could tell it which copy constructor to use - for example:

void f( std::string s );

there is no way of telling the compiler how to copy the string.