public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eng.ahmad.nour at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112838] Compiler is unable to show the exact error location when calling copy ctor for a non-copyable object
Date: Sun, 03 Dec 2023 20:38:48 +0000 [thread overview]
Message-ID: <bug-112838-4-sdEMK8an9E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112838-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112838
--- Comment #2 from Ahmad Nour <eng.ahmad.nour at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> Confirmed, I thought I had saw an issue filed that is very smilar to this.
>
>
> Note clang provides the context:
>
> <source>:5:7: note: in instantiation of member function
> 'std::vector<std::unique_ptr<int>>::vector' requested here
> 5 | class NonCopyable
> | ^
> <source>:14:18: note: in implicit copy constructor for 'NonCopyable' first
> required here
> 14 | NonCopyable b(a);
> | ^
Thanks for confirmation.
I tried with clang-12 -Wall -Wextra main.cpp, but I didn't get that hint/note.
Am I missing something?
next prev parent reply other threads:[~2023-12-03 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 20:10 [Bug c++/112838] New: " eng.ahmad.nour at gmail dot com
2023-12-03 20:27 ` [Bug c++/112838] " pinskia at gcc dot gnu.org
2023-12-03 20:38 ` eng.ahmad.nour at gmail dot com [this message]
2023-12-03 20:53 ` pinskia at gcc dot gnu.org
2023-12-04 11:24 ` redi at gcc dot gnu.org
2023-12-04 11:30 ` redi at gcc dot gnu.org
2023-12-05 8:57 ` eng.ahmad.nour at gmail dot com
2023-12-05 9:01 ` eng.ahmad.nour at gmail dot com
2023-12-05 21:02 ` 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-112838-4-sdEMK8an9E@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).