public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107531] List of references calls destructors, add warning? Date: Sat, 05 Nov 2022 09:12:39 +0000 [thread overview] Message-ID: <bug-107531-4-aNsZCY6QpW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107531-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107531 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Why should the compiler warn here? There are no resources being freed. Making trivial copies and then destroying them is not a bug. If you give the class some resources to manage (e.g. a pointer member) then -Weffc++ will warn that you messed up: dest.C:2:8: warning: ‘struct S’ has pointer data members [-Weffc++] 2 | struct S { | ^ dest.C:2:8: warning: but does not declare ‘S(const S&)’ [-Weffc++] dest.C:2:8: warning: or ‘operator=(const S&)’ [-Weffc++] dest.C:5:10: note: pointer member ‘S::p’ declared here 5 | int* p = nullptr; | ^ It would be nice if you could turn on this warning without the rest of -Weffc++ but that's PR 16166.
next prev parent reply other threads:[~2022-11-05 9:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-05 5:16 [Bug c++/107531] New: " nightstrike at gmail dot com 2022-11-05 5:20 ` [Bug c++/107531] " pinskia at gcc dot gnu.org 2022-11-05 5:27 ` nightstrike at gmail dot com 2022-11-05 9:12 ` redi at gcc dot gnu.org [this message] 2022-11-05 9:15 ` redi at gcc dot gnu.org 2022-11-05 9:29 ` redi 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-107531-4-aNsZCY6QpW@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).