Re: Compiler chooses conv ctor - why?

struct Y {};

class X
{
public:
    X() {}
    X(Y) {}
private:
    X(const X&);
};

int main()
{
    Y y;
    X x1 = y; // ill-formed, inaccessible cctor
    X x2(y); // OK, direct initialization

    return 0;
}

According to the standard `x1' instance cannot be constructed due to
inaccessible copy constructor (which may be eliminated during
construction of an object by the compiler, but the copy semantics
must be preserved anyway).