When a constructor is invoked, although there is no object created till that point, we still know the kind of object that is gonna be created because the specific constructor of the class to which the object belongs to has already been called. Virtual keyword associated with a function means the function of a particular object type is gonna be called. So, my thinking says that there is no need to make the virtual constructor because already the desired constructor whose object is gonna be created has been invoked and making constructor virtual is just a redundant thing to do because the object-specific constructor has already been invoked and this is same as calling class-specific function which is achieved through the virtual keyword. Although the inner implementation won’t allow virtual constructor for vptr and vtable related reasons.

Another reason is that C++ is a statically typed language and we need to know the type of a variable at compile-time. The compiler must be aware of the class type to create the object. The type of object to be created is a compile-time decision. If we make the constructor virtual then it means that we don’t need to know the type of the object at compile-time(that’s what virtual function provide. We don’t need to know the actual object and just need the base pointer to point an actual object call the pointed object’s virtual functions without knowing the type of the object) and if we don’t know the type of the object at compile time then it is against the statically typed languages. And hence, run-time polymorphism cannot be achieved. Hence, Constructor won’t be called without knowing the type of the object at compile-time. And so the idea of making a virtual constructor fails.

When a constructor is invoked, although there is no object created till that point, we still know the kind of object that is gonna be created because the specific constructor of the class to which the object belongs to has already been called. Virtual keyword associated with a function means the function of a particular object type is gonna be called. So, my thinking says that there is no need to make the virtual constructor because already the desired constructor whose object is gonna be created has been invoked and making constructor virtual is just a redundant thing to do because the object-specific constructor has already been invoked and this is same as calling class-specific function which is achieved through the virtual keyword. Although the inner implementation won’t allow virtual constructor for vptr and vtable related reasons.

Another reason is that C++ is a statically typed language and we need to know the type of a variable at compile-time. The compiler must be aware of the class type to create the object. The type of object to be created is a compile-time decision. If we make the constructor virtual then it means that we don’t need to know the type of the object at compile-time(that’s what virtual function provide. We don’t need to know the actual object and just need the base pointer to point an actual object call the pointed object’s virtual functions without knowing the type of the object) and if we don’t know the type of the object at compile time then it is against the statically typed languages. And hence, run-time polymorphism cannot be achieved. Hence, Constructor won’t be called without knowing the type of the object at compile-time. And so the idea of making a virtual constructor fails.

虚函数用于根据指针所指向的对象类型调用函数，而不是指针本身的类型。但是构造函数不会被“调用”。它只在声明对象时调用一次。因此，在c++中构造函数不能被设为虚函数。

“构造函数不能是虚拟的”

有一些合理的理由可以证明这种说法是正确的。

要创建对象，对象类的构造函数必须与类的类型相同。但是，对于虚拟实现的构造函数，这是不可能的。 在调用构造函数时，还没有创建虚表来解析任何虚函数调用。因此，虚拟构造函数本身将没有任何可以查找的地方。

因此，不可能将构造函数声明为虚函数。

你可以在@stefan的回答中找到一个例子和为什么不允许这样做的技术原因。在我看来，这个问题的合理答案是:

virtual关键字的主要用途是在我们不知道基类指针将指向什么类型的对象时启用多态行为。

但这是一种更原始的方式，对于使用虚拟功能，你需要一个指针。指针需要什么?一个指向的对象!(考虑程序正确执行的情况)

因此，我们基本上需要一个已经存在于内存某处的对象(我们不关心内存是如何分配的，它可能是在编译时或运行时)，以便我们的指针能够正确地指向该对象。

现在，想象一下当要指向的类的对象被分配一些内存时的情况——>它的构造函数将在该实例本身被自动调用!

所以我们可以看到，我们实际上不需要担心构造函数是虚的，因为在任何情况下，你希望使用多态行为，我们的构造函数已经执行，使我们的对象准备使用!

面试答案是:virtual ptr和table是和对象相关的，而不是和类相关的。因此构造函数构建虚表 因此，我们不能有虚构造函数，因为在创建obj之前没有虚表。