From: Ulrich Drepper <drepper@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: add more C++ name hints
Date: Wed, 17 Aug 2022 12:29:36 +0200 [thread overview]
Message-ID: <CAP3s5k9p0z-ccFNEd2yMFSmkbErXMHxQ+TGbM_HYn33Le1261w@mail.gmail.com> (raw)
In-Reply-To: <CAP3s5k_2uk-SSPEbZ=Gy_Ri3eAjw8RQH6Nk4fvEDcBYn6fbyEQ@mail.gmail.com>
Any comment on this?
These changes are low-risk so the only real objection I can see is that
people don't deem these messages useful in the first place. I would hope,
though, that some editors/IDEs provide one-click solutions to add the
#includes.
On Fri, Aug 5, 2022 at 9:35 PM Ulrich Drepper <drepper@redhat.com> wrote:
> How about adding a few more names from the std namespace to get
> appropriate hints? This patch compiles and the appropriate messages are
> printed. Is there a problem with just adding more or even at some point
> all the symbols of the standard library?
>
> gcc/ChangeLog:
>
> * cp/name-lookup.cc (get_std_name_hint): Add more symbols from the
> <iomanip>, <ios>, <istream> and <ostream> headers.
>
next prev parent reply other threads:[~2022-08-17 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 19:35 Ulrich Drepper
2022-08-17 10:29 ` Ulrich Drepper [this message]
2022-08-17 12:17 ` Marek Polacek
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=CAP3s5k9p0z-ccFNEd2yMFSmkbErXMHxQ+TGbM_HYn33Le1261w@mail.gmail.com \
--to=drepper@redhat.com \
--cc=gcc-patches@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).