From owner-freebsd-current@FreeBSD.ORG  Tue Nov 12 20:05:34 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 42CA4BDE;
 Tue, 12 Nov 2013 20:05:34 +0000 (UTC)
Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com
 [IPv6:2607:f8b0:400c:c03::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E6F0521E9;
 Tue, 12 Nov 2013 20:05:33 +0000 (UTC)
Received: by mail-vc0-f173.google.com with SMTP id lh4so4605484vcb.18
 for <multiple recipients>; Tue, 12 Nov 2013 12:05:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=jjWpEygFzF9YUIbt0ATZT7B+l9xsYbmBLZtq61hEoVo=;
 b=YAoSRZ6H8bKJsKrhGODrv1kc8YloSeURblG6cFJV4Aue0bIT++5OzdzqODozOtrfJO
 Z1j4iYlKRj2vMTI9TefHQrcJCeYvDACedYKzgrkvBWUZrcWDAwVR/LqYkD/qxCH8MgEz
 CJ7gWxJDELtmBG6fsCxCvTtrLhDgj0w/PrkNoDHST/C4sejndMMD9Gj8jJOJdBw9GbW9
 YdvjDypPdcur9C+xWkv5ho/xR2Qif8Tpg56GuoURT1cmSOKDQ9P0LnadNzpEYctIHozx
 m/oYJcQw0uEP5SHXXs2FDLr2tP4tMbpoJVMCJ0nLDyQARBN57nmn+z1VWB8skHD3qfxh
 gisA==
MIME-Version: 1.0
X-Received: by 10.220.97.145 with SMTP id l17mr1774877vcn.35.1384286732990;
 Tue, 12 Nov 2013 12:05:32 -0800 (PST)
Received: by 10.221.0.145 with HTTP; Tue, 12 Nov 2013 12:05:32 -0800 (PST)
In-Reply-To: <20131112165422.GA2939@troutmask.apl.washington.edu>
References: <20131112163219.GA2834@troutmask.apl.washington.edu>
 <77CB2B92-216A-4C80-B033-7E582B5F0DFC@FreeBSD.org>
 <20131112165422.GA2939@troutmask.apl.washington.edu>
Date: Tue, 12 Nov 2013 15:05:32 -0500
Message-ID: <CAGsORuDPSfp_YQ_Sr8hD9+3e_fEOjE-2uOtXbm+nDvM0neju9Q@mail.gmail.com>
Subject: Re: Are clang++ and libc++ compatible?
From: Zhihao Yuan <lichray@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD current <freebsd-current@freebsd.org>,
 David Chisnall <theraven@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 20:05:34 -0000

On Tue, Nov 12, 2013 at 11:54 AM, Steve Kargl
<sgk@troutmask.apl.washington.edu> wrote:
>       struct Entry {
>         time_t date;
>         Severity severity;
>         std::deque<Entry> messages;
>         std::string message;
>         bool is_child;
>         Entry() : is_child(false) { }
>       };

This is a libc++ QoI issue; T had better not be required to be compete
at the instantiation time of the class template itself.  I've reported this
forward this issue to libc++ upstream.

BTW, iirc VC STL has the same issue.  But libstdc++ has an honorable
history of supporting incomplete type in STL declaration.

-- 
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
___________________________________________________
4BSD -- http://4bsd.biz/