public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lopresti at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109671] Spurious dangling reference warning in GCC 13
Date: Fri, 28 Apr 2023 19:31:39 +0000	[thread overview]
Message-ID: <bug-109671-4-T8ltg3l0ab@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109671-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Patrick J. LoPresti <lopresti at gmail dot com> ---
Um... OK...

So I have to "correct" my code like so:

const Foo &bug(bool x)
{
  const std::string s = (x ? "x" : "y");
  const Foo &f = get_foo_by_name(s);
  return f;
}

But if get_foo_by_name() has the problem GCC is worried about, this does not
even fix it.

This warning seems silly to me. "I cannot tell if you are managing lifetimes
properly, so I will just recommend you do not use temporaries"?

Const references have always bound to temporaries. This warning seems to be
discouraging that (?)

  parent reply	other threads:[~2023-04-28 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 17:48 [Bug c++/109671] New: " lopresti at gmail dot com
2023-04-28 17:51 ` [Bug c++/109671] " pinskia at gcc dot gnu.org
2023-04-28 19:31 ` lopresti at gmail dot com [this message]
2023-05-01  1:15 ` lopresti at gmail dot com
2023-05-02 19:50 ` cvs-commit at gcc dot gnu.org
2024-01-19 17:35 ` 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-109671-4-T8ltg3l0ab@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: link
Be 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).