public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m.cencora at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator Date: Thu, 04 Jan 2024 08:24:01 +0000 [thread overview] Message-ID: <bug-113064-4-kimKiyNaJx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #11 from m.cencora at gmail dot com --- This is surprising to say the least because apparently for following code (where both conversion operators return same type) the compiler somehow correctly chooses && qualified overload: struct bar { bar() = default; bar(const bar&); bar(bar&&); bar& operator=(const bar&); bar& operator=(bar&&); }; struct foo { operator bar() const &; operator bar() &&; }; void test() { bar a = foo{}; // ok a = foo{}; foo f; a = f; // ok } So why cannot it apply the same overload resolution, when conversion operators return different type as in comment #4? Do you think this qualifies for a defect report?
prev parent reply other threads:[~2024-01-04 8:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 12:04 [Bug c++/113064] New: " m.cencora at gmail dot com 2023-12-18 12:41 ` [Bug c++/113064] " m.cencora at gmail dot com 2023-12-18 13:00 ` m.cencora at gmail dot com 2023-12-18 19:58 ` mpolacek at gcc dot gnu.org 2023-12-19 9:10 ` m.cencora at gmail dot com 2023-12-19 11:39 ` m.cencora at gmail dot com 2023-12-19 15:54 ` mpolacek at gcc dot gnu.org 2024-01-03 20:43 ` cvs-commit at gcc dot gnu.org 2024-01-03 22:35 ` ppalka at gcc dot gnu.org 2024-01-03 22:36 ` ppalka at gcc dot gnu.org 2024-01-03 22:50 ` ppalka at gcc dot gnu.org 2024-01-04 8:24 ` m.cencora at gmail dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113064-4-kimKiyNaJx@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).