public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "herring at lanl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94231] New: Invalid move constructor defaulted outside of class as deleted is accepted Date: Fri, 20 Mar 2020 00:08:04 +0000 [thread overview] Message-ID: <bug-94231-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94231 Bug ID: 94231 Summary: Invalid move constructor defaulted outside of class as deleted is accepted Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: herring at lanl dot gov Target Milestone: --- GCC incorrectly accepts the following: struct F {F(F&&)=delete;}; template<int=0> struct M { F f; M(); M(const M&); M(M&&); }; template<int I> M<I>::M(M&&)=default; M<> f() { M<> m; return m; } The returned value is implicitly moved-from (although adding static_cast<M<>&&> makes no difference), which should discover that M's move constructor is invalid because it is defaulted after its first declaration and defined as deleted, but simply falls back to the copy constructor instead. If M is not a template, GCC correctly rejects, although the error messages are a bit confused.
next reply other threads:[~2020-03-20 0:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-20 0:08 herring at lanl dot gov [this message] 2020-04-18 0:06 ` [Bug c++/94231] " mpolacek at gcc dot gnu.org 2024-02-06 14:36 ` mpolacek at gcc dot gnu.org 2024-02-06 16:49 ` cvs-commit at gcc dot gnu.org 2024-02-06 16:51 ` mpolacek at gcc dot gnu.org
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-94231-4@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).