public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeff at schwabcenter dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/40192] [4.4/4.5 Regression] Unable to use std::vector with typedef'd array types Date: Tue, 19 May 2009 18:07:00 -0000 [thread overview] Message-ID: <20090519180748.21818.qmail@sourceware.org> (raw) In-Reply-To: <bug-40192-17730@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from jeff at schwabcenter dot com 2009-05-19 18:07 ------- What he said. I'm perusing your patch, and I appreciate that you removed an artificial restriction. The right place to catch this is up front, in a concept check, rather than in _Destroy; since I'm not about to add the check myself, I'm hardly in a position to criticize. The diagnostic did have the nice property of catching a real, semantic error, though, and it seems a shame to let a known error go unreported. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40192
next prev parent reply other threads:[~2009-05-19 18:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-18 21:06 [Bug c++/40192] New: " coleb at eyesopen dot com 2009-05-18 22:34 ` [Bug c++/40192] [4.4/4.5 Regression] " paolo dot carlini at oracle dot com 2009-05-18 23:16 ` paolo at gcc dot gnu dot org 2009-05-18 23:17 ` paolo at gcc dot gnu dot org 2009-05-18 23:18 ` paolo dot carlini at oracle dot com 2009-05-19 16:36 ` jeff at schwabcenter dot com 2009-05-19 16:42 ` paolo dot carlini at oracle dot com 2009-05-19 17:09 ` jeff at schwabcenter dot com 2009-05-19 17:12 ` paolo dot carlini at oracle dot com 2009-05-19 17:33 ` jeff at schwabcenter dot com 2009-05-19 17:38 ` paolo dot carlini at oracle dot com 2009-05-19 17:58 ` coleb at eyesopen dot com 2009-05-19 18:07 ` jeff at schwabcenter dot com [this message] 2009-05-19 18:19 ` paolo dot 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=20090519180748.21818.qmail@sourceware.org \ --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).