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++/95659] Inconsistent error message in "default argument missing for parameter"
Date: Thu, 18 Jun 2020 11:34:42 +0000	[thread overview]
Message-ID: <bug-95659-4-Ma2CL966Zg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95659-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95659

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Haoxin Tu from comment #0)
> $cat bug.cc
> int a;
> long  foo1 ( void  = a, double  param2 ,decltype (auto) param3 = a){ }
> long  foo2 ( void  = a, double  param2){ }
> 
> In gcc-trunk
> $g++-trunk -w -c -std=c++14 bug.cc 
> bug.cc:2:41: error: cannot declare a parameter with ‘decltype(auto)’
>     2 | long  foo1 ( void  = a, double  param2 ,decltype (auto) param3 = a){
> }
>       |                                         ^~~~~~~~~~~~~~~
> bug.cc:2:14: error: invalid use of type ‘void’ in parameter declaration
>     2 | long  foo1 ( void  = a, double  param2 ,decltype (auto) param3 = a){
> }
>       |              ^~~~~~~~~

The first two errors are correct, the function declaration is complete garbage
and these errors correctly identify some of the problems.

Whether it *also* notices another error in this garbage doesn't really matter.
You need to fix this nonsense before the code can be compiled anyway.

The general rule of thumb is always to start by fixing the first errors,
because they might be causing the later ones. If you fix those two errors, then
G++ will  tell you about the next problem.

It's not really helpful to keep pointing out that if you randomly generate
complete garbage then GCC gets confused.

  reply	other threads:[~2020-06-18 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 17:32 [Bug c++/95659] New: " haoxintu at gmail dot com
2020-06-18 11:34 ` redi at gcc dot gnu.org [this message]
2024-05-09  9:09 ` [Bug c++/95659] " redi 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-95659-4-Ma2CL966Zg@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).