[Bug c++/77386] Explicit constructor is allowed causing ambiguous initialization call when it shouldn't be allowed

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77386

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
See PR 60027 comment 1 which argues this is what the standard requires (which
is unfortunate IMHO).

*** This bug has been marked as a duplicate of bug 60027 ***