public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53248] std::array<T,0> doesn't work when T is not default-constructible Date: Sat, 05 May 2012 23:57:00 -0000 [thread overview] Message-ID: <bug-53248-4-DnualLIl0J@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53248-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53248 --- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-05-05 23:27:26 UTC --- The basic design of our std::array is rather old, dates back to the tr1::array times, with updates. I bet we simply overlooked this issue, in terms of QoI. Daniel, can you see other options besides adding a specialization? (which would be a straightforward task, I may even get around to do pretty soon when I will do debug-mode std::array, already in my todo list)
next prev parent reply other threads:[~2012-05-05 23:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-05 20:14 [Bug libstdc++/53248] New: " dwalker07 at yahoo dot com 2012-05-05 21:59 ` [Bug libstdc++/53248] " daniel.kruegler at googlemail dot com 2012-05-05 23:57 ` paolo.carlini at oracle dot com [this message] 2012-05-06 11:41 ` daniel.kruegler at googlemail dot com 2012-05-06 15:42 ` paolo.carlini at oracle dot com 2012-05-06 18:56 ` paolo.carlini at oracle dot com 2012-05-06 19:19 ` daniel.kruegler at googlemail dot com 2012-05-06 19:56 ` paolo.carlini at oracle dot com 2012-10-01 23:44 ` paolo.carlini at oracle dot com 2012-10-04 0:02 ` paolo at gcc dot gnu.org 2012-10-04 0:03 ` 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-53248-4-DnualLIl0J@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).