public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53648] [C++11] nested empty tuples Date: Tue, 12 Jun 2012 17:28:00 -0000 [thread overview] Message-ID: <bug-53648-4-6CkbOqazBp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53648-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53648 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-06-12 17:27:50 UTC --- There are other cases involving non-empty tuples that will still result in an ambiguity e.g. struct A { }; auto d = tuple<tuple<tuple<A, A>, A>, A>{}; My solution avoids using the EBO for some condition I don't remember (the code's on another machine) but it handles all the cases I tested. I also preserve the property that sizeof(tuple<char, tuple<>>)==1, which I think your suggestion loses.
next prev parent reply other threads:[~2012-06-12 17:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-12 16:22 [Bug c++/53648] New: nested empty tuple chesstr at hotmail dot com 2012-06-12 16:42 ` [Bug c++/53648] nested empty tuples redi at gcc dot gnu.org 2012-06-12 17:13 ` [Bug libstdc++/53648] [C++11] " chesstr at hotmail dot com 2012-06-12 17:28 ` redi at gcc dot gnu.org [this message] 2012-06-12 18:04 ` chesstr at hotmail dot com 2012-06-14 22:07 ` redi at gcc dot gnu.org 2012-06-14 22:12 ` redi 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-53648-4-6CkbOqazBp@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).