[Bug c++/65869] Incorrect overload resolution in function return statement

[botond at mozilla dot com]

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

--- Comment #4 from Botond Ballo <botond at mozilla dot com> ---
>   - The second overload resolution fails, because the only
>     candidate (again, the explicit constructors are not
>     candidates) has an rvalue reference parameter, which
>     cannot bind to the lvalue that we're not treating the
>     object as being.

This is also a typo, should say "cannot bind to the lvalue that we're treating
the object as being".