This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [v3] First bits of libstdc++/44436

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Fri, 29 Oct 2010 17:09:52 +0200
Subject: Re: [v3] First bits of libstdc++/44436
References: <4CC9A0CD.5000600@oracle.com>

On 10/28/2010 06:11 PM, Paolo Carlini wrote:
> However, I'd like to ask your help (I'm addressing in particular the
> library people of course) in figuring out a long term solution for the
> _Select1st function object: the one we traditionally use in C++03 mode
> doesn't work with move-semantics, because insists on using
> container::value_type (the -2 testcases would not compile with it). For
> the associative containers I guess the situation will be completely
> similar and I'd like to figure out a satisfactory solution looking
> forward, possibly improving the std::_Select1st itself and just using it
> everywhere. Is __detail::_Select1st already ok for C++0x mode or we want
> something better?
>   
About this issue, I'm committing the below, a definite improvement,
IMHO. With it, the associative containers should also be ok.

Tested x86_64-linux

Paolo.

/////////////////////////////

Attachment: CL_select1st
Description: Text document

Attachment: patch_select1st
Description: Text document

References:
- [v3] First bits of libstdc++/44436
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]