From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21842 invoked by alias); 19 May 2009 18:07:59 -0000 Received: (qmail 21819 invoked by uid 48); 19 May 2009 18:07:48 -0000 Date: Tue, 19 May 2009 18:07:00 -0000 Message-ID: <20090519180748.21818.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/40192] [4.4/4.5 Regression] Unable to use std::vector with typedef'd array types In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jeff at schwabcenter dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg01646.txt.bz2 ------- 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