Why is copy constructor called instead of conversion constructor?

前端 未结 1 911
无人及你
无人及你 2020-11-30 02:19

So basically this code:

class A {
};
class B { 
   B (const B& b) {}
public: 
   B (){}
   B (const A& a) {} 
};

int main()
{
   A a;
   B b1(a);  /         


        
相关标签:
1条回答
  • 2020-11-30 02:46
    B b2 = a;
    

    This is known as Copy Initialization.

    It does the following:

    1. Create an object of type B from a by using B (const A& a).
    2. Copy the created temporary object to b2 by using B (const B& b).
    3. Destroy the temporary object by using ~B().

    The error you get is not at step 1 but rather at step 2.

    Where is this in the standard?

    C++03 8.5 Initializers
    Para 14:

    ....
    — If the destination type is a (possibly cv-qualified) class type:
    ...
    ...
    — Otherwise (i.e., for the remaining copy-initialization cases), user-defined conversion sequences that can convert from the source type to the destination type or (when a conversion function is used) to a derived class thereof are enumerated as described in 13.3.1.4, and the best one is chosen through overload resolution (13.3). If the conversion cannot be done or is ambiguous, the initialization is ill-formed. The function selected is called with the initializer expression as its argument; if the function is a constructor, the call initializes a temporary of the destination type. The result of the call (which is the temporary for the constructor case) is then used to direct-initialize, according to the rules above, the object that is the destination of the copy-initialization. In certain cases, an implementation is permitted to eliminate the copying inherent in this direct-initialization by constructing the intermediate result directly into the object being initialized; see 12.2, 12.8.

    0 讨论(0)
提交回复
热议问题