public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "leonid at volnitsky dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55002] New: trailing return type is rejected in function signature Date: Sat, 20 Oct 2012 19:01:00 -0000 [thread overview] Message-ID: <bug-55002-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55002 Bug #: 55002 Summary: trailing return type is rejected in function signature Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: leonid@volnitsky.com 7.1.6.4 auto specifier [dcl.spec.auto] note 2: The auto type-specifier may appear with a function declarator with a trailing-return-type (8.3.5) in any context where such a declarator is valid Contrived example: ------------------------------------------------------------- typedef unsigned long size_t; // overload c-array template<class T, size_t N> size_t size(T (&)[N]) { return N; } // overload - c-string template<size_t N> size_t size(char (&A)[N]) { size_t i=0; while(A[i++]); return i; } // APPLY // this works template<class T, size_t N> size_t apply (const T (&A)[N], size_t (*f) (const T (&)[N])) // this rejected -- error: parameter declared ‘auto’ //template<class T, size_t N> size_t apply (const T (&A)[N], auto (*f) -> size_t (const T (&)[N])) { return f(A); }; int main() { int A[2]; return apply(A, size); } ------------------------------------------------------------------ Without trailing return type in signature it is impossible to write apply-like function with can deduce function-type for overloaded functions.
next reply other threads:[~2012-10-20 19:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-20 19:01 leonid at volnitsky dot com [this message] 2012-10-20 19:20 ` [Bug c++/55002] " leonid at volnitsky dot com 2012-10-20 20:24 ` daniel.kruegler at googlemail dot com 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@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).