public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55002] trailing return type is rejected in function signature Date: Sat, 20 Oct 2012 20:24:00 -0000 [thread overview] Message-ID: <bug-55002-4-oclvQcfQaE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55002-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55002 Daniel Krügler <daniel.kruegler at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.kruegler at | |googlemail dot com --- Comment #2 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2012-10-20 20:24:19 UTC --- Your issue looks invalid to me, because you are never providing a pointer to function declarator. Lets look first at your simplified example: auto (*ff) -> int (int) This would be an invalid function declarator, because there is (a) no parameter list and (b) the return type is a function type int(int), which is never possible. I can only assume you mean int f(auto (*ff)(int) -> int) { return ff(1); } and this is accepted. A similar defect is in your original code, where the only valid form would be template<class T, size_t N> size_t apply (const T (&A)[N], auto (*f)(const T (&)[N]) -> size_t) { return f(A); } which is also accepted.
next prev parent reply other threads:[~2012-10-20 20:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-20 19:01 [Bug c++/55002] New: " leonid at volnitsky dot com 2012-10-20 19:20 ` [Bug c++/55002] " leonid at volnitsky dot com 2012-10-20 20:24 ` daniel.kruegler at googlemail dot com [this message] 2012-10-20 22:56 ` paolo.carlini at oracle dot com
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-55002-4-oclvQcfQaE@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).