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: [v3] Implement resolution of DR 630

From: Jason Merrill <jason at redhat dot com>
To: Paolo Carlini <paolo dot carlini at oracle dot com>
Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Thu, 23 Jul 2009 17:48:07 -0400
Subject: Re: [v3] Implement resolution of DR 630
References: <4A670520.6090801@oracle.com>

On 07/22/2009 08:25 AM, Paolo Carlini wrote:

-- Jason, while working on this issue, I noticed that:

     valarray<int>  v1;
     v1 = { };

compiles just fine in -std=c++0x mode and, for the assignment, ends up
being selected:

operator=(const Tp&)

with Tp == 0. On the other hand, in C++03 mode, the snippet doesn't
compile at all. Could you please confirm the above is the expected
behavior? Thanks in advance!

Actually, yes, that's what the current draft says should happen. Though it may not be what we want to happen.

Jason

Follow-Ups:
- Re: [v3] Implement resolution of DR 630
  - From: Paolo Carlini
- Re: [v3] Implement resolution of DR 630
  - From: Jason Merrill

References:
- [v3] Implement resolution of DR 630
  - From: Paolo Carlini

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