public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41426] User defined conversion on return ignores array types Date: Thu, 14 Jul 2011 16:05:00 -0000 [thread overview] Message-ID: <bug-41426-4-kJzCRuwNnH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41426-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41426 Ville Voutilainen <ville.voutilainen at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ville.voutilainen at gmail | |dot com --- Comment #1 from Ville Voutilainen <ville.voutilainen at gmail dot com> 2011-07-14 16:04:11 UTC --- gcc 4.7 (trunk) still behaves this way. An example snippet was provided for me: struct v { template<unsigned N> v( const char(&)[N] ){} }; v foo( ) { return "Hello WOrld"; // #1 } int main ( ) { v x("hello world"); // #2 } in that snippet, #1 is rejected with error: could not convert ‘(const char*)"Hello WOrld"’ from ‘const char*’ to ‘v’ Explicit construction of v in foo() works.
parent reply other threads:[~2011-07-14 16:05 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-41426-4@http.gcc.gnu.org/bugzilla/>]
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-41426-4-kJzCRuwNnH@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).