public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102773] Show fix-its for mispelled keywords like "templat" and "clas" and "typname" Date: Thu, 27 Oct 2022 10:50:47 +0000 [thread overview] Message-ID: <bug-102773-4-wE593OdAeK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102773 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-10-27 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Another example: long i = reintepret_cast<long>((void*)0); cast.C:1:10: error: ‘reintepret_cast’ was not declared in this scope 1 | long i = reintepret_cast<long>((void*)0); | ^~~~~~~~~~~~~~~ cast.C:1:26: error: expected primary-expression before ‘long’ 1 | long i = reintepret_cast<long>((void*)0); | ^~~~ And this one with -std=c++20: template<class T> void f(const void* v) { auto u = reintepret_cast<long>(v); } cast.C: In function 'void f(const void*)': cast.C:5:12: error: there are no arguments to 'reintepret_cast' that depend on a template parameter, so a declaration of 'reintepret_cast' must be available [-fpermissive] 5 | auto u = reintepret_cast<long>(v); | ^~~~~~~~~~~~~~~~~~~~~ cast.C:5:12: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
prev parent reply other threads:[~2022-10-27 10:50 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 11:50 [Bug c++/102773] New: " redi at gcc dot gnu.org 2022-10-27 10:50 ` redi at gcc dot gnu.org [this message]
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-102773-4-wE593OdAeK@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: linkBe 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).