public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ethouris at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104343] New: Too many arguments error reported for a variadic-argument function if std::endl is passed Date: Wed, 02 Feb 2022 13:19:12 +0000 [thread overview] Message-ID: <bug-104343-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104343 Bug ID: 104343 Summary: Too many arguments error reported for a variadic-argument function if std::endl is passed Product: gcc Version: 7.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ethouris at gmail dot com Target Milestone: --- I have the following definition (requires `<string>` and `<stringstream>`): ``` template <class Stream> inline Stream& Print(Stream& in) { return in;} template <class Stream, class Arg1, class... Args> inline Stream& Print(Stream& sout, Arg1&& arg1, Args&&... args) { sout << arg1; return Print(sout, args...); } template <class... Args> inline std::string Sprint(Args&&... args) { std::ostringstream sout; Print(sout, args...); return sout.str(); } ``` The call ``` sinfo.bufferinfo = Sprint("B: off=", buffer.offset(), " now=", FormatTime(timeinfo), endl); ``` Reports this error: ``` (5 of 13): error: too many arguments to function 'std::__cxx11::string Sprint(Args&& ...) [with Args = {}; std::__cxx11::string = std::__cxx11::basic_string<char>]' ``` Replacing `endl` with `"\n"` fixes the problem. Might be that I cannot bind `std::endl` to the argument as given here, but the error report is at least misleading. How can there be "too many arguments" passed to a function that gets a variable number of arguments?
next reply other threads:[~2022-02-02 13:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-02 13:19 ethouris at gmail dot com [this message] 2022-02-02 14:17 ` [Bug c++/104343] " rguenth at gcc dot gnu.org 2022-02-02 17:13 ` redi at gcc dot gnu.org 2022-02-02 17:15 ` redi at gcc dot gnu.org 2022-02-02 17:31 ` redi at gcc dot gnu.org 2022-02-02 17:33 ` redi at gcc dot gnu.org 2022-02-02 21:25 ` [Bug c++/104343] improved error message for passing overloaded function to variadic-argument function pinskia at gcc dot gnu.org 2024-03-16 18:11 ` [Bug c++/104343] improved error message for passing overloaded function to variadic(templated)-argument function pinskia at gcc dot gnu.org 2024-03-17 6:07 ` f.heckenbach@fh-soft.de 2024-03-17 6:17 ` 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-104343-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).