public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schaub.johannes at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/55713] std::tuple<ElementType> incorrectly is convertible to "ElementType" when it is an empty class Date: Sun, 16 Dec 2012 17:52:00 -0000 [thread overview] Message-ID: <bug-55713-4-tIYfpIee5L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55713-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55713 --- Comment #2 from Johannes Schaub <schaub.johannes at googlemail dot com> 2012-12-16 17:52:14 UTC --- (In reply to comment #1) > This was done for an optimization. And I think it is allowed by the C++ > standard too. >From the feedback I received from Stackoverflow ( http://stackoverflow.com/q/13902910/34509 ) I assumed that this behavior is not permissible. There also appear to be ways to make it not behave that way (see LLVM libc++'s implementation).
next prev parent reply other threads:[~2012-12-16 17:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-16 16:46 [Bug libstdc++/55713] New: " schaub.johannes at googlemail dot com 2012-12-16 17:49 ` [Bug libstdc++/55713] " pinskia at gcc dot gnu.org 2012-12-16 17:52 ` schaub.johannes at googlemail dot com [this message] 2012-12-16 20:40 ` redi at gcc dot gnu.org 2012-12-16 22:48 ` glisse at gcc dot gnu.org 2020-03-19 12:38 ` redi at gcc dot gnu.org 2020-08-07 17:33 ` redi at gcc dot gnu.org 2020-08-17 14:29 ` cvs-commit at gcc dot gnu.org 2020-08-17 14:31 ` redi at gcc dot gnu.org 2021-12-22 18:29 ` jason 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-55713-4-tIYfpIee5L@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).