public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "f.heckenbach@fh-soft.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114362] New: wrong error message "too many arguments" with overloaded function Date: Sat, 16 Mar 2024 09:12:48 +0000 [thread overview] Message-ID: <bug-114362-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114362 Bug ID: 114362 Summary: wrong error message "too many arguments" with overloaded function Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: f.heckenbach@fh-soft.de Target Milestone: --- % cat test.cpp #include <tuple> void f (); void f (int); void g () { std::tie (f) = 0; } % g++ test.cpp test.cpp: In function 'void g()': test.cpp:8:12: error: too many arguments to function 'constexpr std::tuple<_Elements& ...> std::tie(_Elements& ...) [with _Elements = {}]' [...] This only happens when f is overloaded. When I comment out either of the two declarations of f, I get only "error: no match for 'operator='" as expected.
next reply other threads:[~2024-03-16 9:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 9:12 f.heckenbach@fh-soft.de [this message] 2024-03-16 18:11 ` [Bug c++/114362] " 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-114362-4@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).