This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: [c++0x] Ambiguity using std::to_string

From: Christopher Jefferson <chris at bubblescope dot net>
To: Paolo Carlini <paolo dot carlini at oracle dot com>
Cc: Germán Diago <germandiago at gmail dot com>, libstdc++ at gcc dot gnu dot org
Date: Tue, 10 Nov 2009 16:38:11 +0000
Subject: Re: [c++0x] Ambiguity using std::to_string
References: <b798010f0911100024j7d509756x39f2ac3eab5236de@mail.gmail.com> <99A2D883-81AC-440E-80BB-2FFB9430C25F@bubblescope.net> <4AF98A14.6090600@oracle.com>

On 10 Nov 2009, at 15:43, Paolo Carlini wrote:

> Christopher Jefferson wrote:
>> I agree with you. I think this is a case of someone trying to be too clever, and not realising that the set of overloads they specified was not enough.
>> 
> I agree. Probably we should simply file a DR. Chris, care to ask the
> library reflector, just in case we are missing something?

Yes, on the case, will submit DR and get a discussion going. However this is fixed, the current situation is clearly embarrassing.

Chris

Follow-Ups:
- Re: [c++0x] Ambiguity using std::to_string
  - From: Germán Diago

References:
- [c++0x] Ambiguity using std::to_string
  - From: Germán Diago
- Re: [c++0x] Ambiguity using std::to_string
  - From: Christopher Jefferson
- Re: [c++0x] Ambiguity using std::to_string
  - From: Paolo Carlini

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