public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107363] Wrong caret location for "redundant move in return statement" and nvo
Date: Mon, 24 Oct 2022 16:34:44 +0000 [thread overview]
Message-ID: <bug-107363-4-KhNxzgiA0a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107363-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107363
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-10-24
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
CC| |mpolacek at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Daniel Bertalan from comment #0)
> As an aside, it's a bit annoying to have this warning when the moved type
> depends on a template parameter in library code. We are forced to either
> silence this warning with a #pragma, or use concepts to have a variant of
> the release_value method that does not call std::move for const-qualified T.
Understood, I thought I'd fixed cases like that in
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6602a2b2dee16af6e2d451c704789356042b5881
Something's not right here. I need to take a closed look. Thanks for
reporting the bug.
next prev parent reply other threads:[~2022-10-24 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 9:43 [Bug c++/107363] New: Wrong caret location for "redundant move in return statement" dani at danielbertalan dot dev
2022-10-23 15:52 ` [Bug c++/107363] Wrong caret location for "redundant move in return statement" and nvo pinskia at gcc dot gnu.org
2022-10-24 16:34 ` mpolacek at gcc dot gnu.org [this message]
2022-11-09 2:37 ` cvs-commit at gcc dot gnu.org
2022-11-09 2:52 ` mpolacek at gcc dot gnu.org
2022-11-28 22:17 ` pinskia 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-107363-4-KhNxzgiA0a@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).