public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104806] Weird error message: did you mean "__dt "
Date: Tue, 08 Mar 2022 20:43:04 +0000 [thread overview]
Message-ID: <bug-104806-4-CwtSLetDnO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104806-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104806
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:e480c3c06d20874fd7504bfdcca0b829f8000389
commit r12-7544-ge480c3c06d20874fd7504bfdcca0b829f8000389
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Mar 8 21:41:21 2022 +0100
c++: Don't suggest cdtor or conversion op identifiers in spelling hints
[PR104806]
On the following testcase, we emit "did you mean '__dt '?" in the error
message. "__dt " shows there because it is dtor_identifier, but we
shouldn't suggest those to the user, they are purely internal and can't
be really typed by the user because of the final space in it.
2022-03-08 Jakub Jelinek <jakub@redhat.com>
PR c++/104806
* search.cc (lookup_field_fuzzy_info::fuzzy_lookup_field): Ignore
identifiers with space at the end.
* g++.dg/spellcheck-pr104806.C: New test.
next prev parent reply other threads:[~2022-03-08 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 13:15 [Bug c++/104806] New: " jengelh at inai dot de
2022-03-06 20:53 ` [Bug c++/104806] " pinskia at gcc dot gnu.org
2022-03-07 8:56 ` rguenth at gcc dot gnu.org
2022-03-07 9:50 ` jakub at gcc dot gnu.org
2022-03-08 20:43 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-08 20:46 ` jakub at gcc dot gnu.org
2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org
2022-05-10 8:25 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:25 ` cvs-commit 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-104806-4-CwtSLetDnO@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).