why in singleton pattern , we do make copy constructor and assignment operator as private?

Question

In a singleton pattern, typically we make the constructor/destructor private. That I understand because we don't want the user to create/delete the singleton object. There should be only way to get or create the instance. However, I don't understand why do we need to make the copy constructor and assignment operator as private. What is the advantage of making the copy constructor and assignment operator private in singleton.

Answer 1

Singleton obj1 = Singleton::CreateInstacnce();
    Singleton obj2 = obj1; // copy ctr gets called
    Singleton obj3;
    obj3 = obj1;  // assignment operator gets called

Therefore, if you don't make them private, multiple instance of Singleton class will be created

Answer 2

If you copy a singleton, you will have two objects of the same type. The purpose of singleton is to enforce only one instance. Copying would break that assumption.

Answer 3

In a singleton pattern, we just want to instantiate only one object. As you said, we we don't want the user to create/delete the singleton object, and we also don't want the user to copy the second object.

Answer 4

Singleton obj1 = Singleton::CreateInstacnce();
    Singleton obj2 = obj1; // copy ctr gets called
    Singleton obj3;
    obj3 = obj1;  // assignment operator gets called

Here as per my opinion I feel only copy ctr should be private along with constructor.

No need to make Assignment operator as private since Singleton obj3; will anyways give the error saying that Singleton () is private.