Date: Tue, 12 Nov 2013 15:05:32 -0500 From: Zhihao Yuan <lichray@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: FreeBSD current <freebsd-current@freebsd.org>, David Chisnall <theraven@freebsd.org> Subject: Re: Are clang++ and libc++ compatible? Message-ID: <CAGsORuDPSfp_YQ_Sr8hD9%2B3e_fEOjE-2uOtXbm%2BnDvM0neju9Q@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGsORuDPSfp_YQ_Sr8hD9%2B3e_fEOjE-2uOtXbm%2BnDvM0neju9Q>