N4014: Uniform Copy Initialization -- Nicolai Josuttis

By Blog Staff | May 27, 2014 05:33 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4014

Date: 2014-05-25

Uniform Copy Initialization

by Nicolai Josuttis

Excerpt:

C++ distinguishes between copy initialization and direct initialization (see 8.5 §17).

This has the effect that an explicit in a constructor disables copy initialization, while direct initialization is still supported.

This proposal suggests to deal with copy initializations as with direct initializations.

N4007: Delimited iterators (Rev. 2) -- Mike Spertus

By Blog Staff | May 27, 2014 05:31 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4007

Date: 2014-05-25

Delimited iterators (Rev. 2)

by Mike Spertus

Excerpt:

... In the LEWG discussion of N3581 in Issaquah, it was pointed out that the interactions of this proposal were unexpectedly subtle, so the authors wish to discuss the design decisions in more detail. ...

N4006: An improved emplace() for unique-key maps -- Thomas Köppe

By Blog Staff | May 27, 2014 05:26 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4006

Date: 2014-05-26

An improved emplace() for unique-key maps

by Thomas Köppe

Excerpt:

The author had initially proposed in N3873 to add new specialised algorithms to unique-key maps, ... When that paper was presented in Issaquah in February 2014, Jeffrey Yasskin created LWG 2362 to track the core problem, namely the lack of specification of whether moving-from happens. At the meeting, there seems to have been a strong consensus that emplace should “just work”, but that no progress could be made until a concrete proposal had been worked out. At the same time, new algorithms should not be added, and a fixed emplace would provide the desired functionality. It was also recognized that fixing emplace would not be trivial and that there would need to be a way to extract the key from the arguments.

N3996: Static reflection -- Matúš Chochlík

By Blog Staff | May 27, 2014 05:22 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3996

Date: 2014-05-26

Static reflection

by Matúš Chochlík

Excerpt:

Reflection and reflective programming can be used for a wide range of tasks such as implementation of serialization-like operations, remote procedure calls, scripting, automated GUI-generation, implementation of several software design patterns, etc. C++ as one of the most prevalent programming languages lacks a standardized reflection facility.

N3980: Types Don't Know # -- Howard Hinnant

By Blog Staff | May 27, 2014 05:20 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3980

Date: 2014-05-24

Types Don't Know #

by Howard Hinnant

Excerpt:

This paper proposes a new hashing infrastructure that completely decouples hashing algorithms from individual types that need to be hashed. This decoupling divides the hashing computation among 3 different programmers who need not coordinate with each other: ...

To start off with, we emphasize: there is nothing in this proposal that changes the existing std::hash, or the unordered containers. And there is also nothing in this proposal that would prohibit the committee from standardizing both this proposal, and either one of N3333 or N3876.

N3978: C++ Ostream Buffers -- Lawrence Crowl, Peter Sommerlad

By Blog Staff | May 27, 2014 05:17 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N3978

Date: 2014-05-26

C++ Ostream Buffers

by Lawrence Crowl, Peter Sommerlad

Excerpt:

At present, stream output operations guarantee that they will not produce race conditions, but do not guarantee that the effect will be sensible. Some form of external synchronization is required. Unfortunately, without a standard mechanism for synchronizing, independently developed software will be unable to synchronize. ...

The general consensus in the July 2013 meeting of the Concurrency Study Group was that buffering should be explicit. This paper proposes such an explicit buffering.

N4039: Default executor -- Adam Berkan, Chris Mysen, Hans Boehm

By Blog Staff | May 27, 2014 04:12 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4039

Date: 2014-05-23

Default executor

by Adam Berkan, Chris Mysen, Hans Boehm

Excerpt:

So far the standard has been quiet about whether there is a default executor (See n3785 for more about executors).  A well-written library that wishes to be flexible should take an executor as a parameter.  Unfortunately there is today no good default for that library.  Programmers want a way to run tasks asynchronously without having to create new executors. ...

We’ve been discussing a number of proposals;  they all have pros and cons.  They all center around 3 new standard executors: ... We don’t think any specific favorite proposal is obviously the best, but would like to hear what others think...

N3967-69: Library Issues Lists -- Alisdair Meredith

By Blog Staff | May 27, 2014 04:08 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document numbers: N3967-69

Date: 2014-03-24

C++ Standard Library Active Issues List (Revision R88)

C++ Standard Library Defect Report List (Revision R88)

C++ Standard Library Closed Issues List (Revision R88)

by Alisdair Meredith

N4043: Dynarray Allocation Context -- Lawrence Crowl

By Blog Staff | May 27, 2014 03:48 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4043

Date: 2014-05-22

Dynarray Allocation Context

by Lawrence Crowl

Excerpt:

Introduction

The dynarray class (N3662 C++ Dynamic Arrays and N3820 Working Draft, Technical Specification — Array Extensions) and any other named class attempting to use the execution stack for allocation may suffer failure if the class is reallocated with in-place destruction and a placement new. This problem is described in N3899 Nested Allocation section Nested Lifetime. We need specific wording to address this case.

Solution

We choose to permit the stack optimization for constructors called an automatic variables and then only if not called with the placement new operator. This change effectively requires the compiler to recognize the context of a constructor call and, when appropriate, change the implementation to an alternate implementation.

N4042: Safe conversions in unique_ptr<T[]> -- Geoffrey Romer

By Blog Staff | May 27, 2014 03:44 PM | Tags: None

A new WG21 paper is available. A copy is linked below, and the paper will also appear in the next normal WG21 mailing. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.

Document number: N4042

Date: 2014-05-23

Safe conversions in unique_ptr<T[]>

by Geoffrey Romer

Excerpt:

This paper proposes to resolve LWG 2118 by permitting conversions to unique_ptr<T[]> if they are known to be safe.