Document number: N3821-23

Date: 2013-10-14

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

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

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

by Alisdair Meredith

The purpose of this document is to record the status of issues which have come before the Library Working Group (LWG) of the INCITS PL22.16 and ISO WG21 C++ Standards Committee.

Document number: N3819

Date: 2013-10-11

Concepts Lite Specification

by Andrew Sutton

C++ has long provided language support for generic programming in the form of templates. However, these templates are unconstrained, allowing any type or value to be substituted for a template argument, often resulting in compiler errors. What is lacking is a specification of an interface for a template, separate from its implementation, so that a use of a template can be selected among alternative templates and checked in isolation.

Document number: N3818

Date: 2013-10-11

Centralized Defensive-Programming Support for Narrow Contracts (Revision 2)

by John Lakos, Alexei Zakharov

In this proposal, we describe a centralized facility for supporting defensive runtime validation of function preconditions.

Document number: N3817

Date: 2013-10-11

C++ Latches and Barriers

by Alasdair Mackintosh

We propose a set of commonly-used concurrency classes, some of which may be implemented using efficient lock-free algorithms where appropriate. This paper describes the latch and barrier classes.

Latches are a thread co-ordination mechanism that allow one or more threads to block until an operation is completed. An individual latch is a single-use object; once the operation has been completed, it cannot be re-used.

Barriers are a thread co-ordination mechanism that allow multiple threads to block until an operation is completed. Unlike a latch, a barrier is re-usable; once the operation has been completed, the threads can re-use the same barrier. It is thus useful for managing repeated tasks handled by multiple threads.

A reference implementation of these two classes has been written.

Document number: N3816

Date: 2013-10-13

Polymorphic Memory Resources - r1

by Pablo Halpern

A significant impediment to effective memory management in C++ has been the inability to use allocators in non-generic contexts...

Document number: N3815

Date: 2013-10-03

Enumerator List Property Queries

by Andrew Tomazos, Christian Käser

We propose to add three Property Queries [meta.unary.prop.query] to the Metaprogramming and Type Traits Standard Library that provide compile-time access to the enumerator-list of an enumeration type.

Document number: N3814

Date: 2013-10-06

Call for Compile-Time Reflection Proposals

by Jeff Snyder, Chandler Carruth

The reflection study group (SG7) of the C++ standards committee is soliciting proposals for features that add compile-time reflection capabilities to C++. Whilst all proposals regarding reflection in C++ will be considered, the group's current focus is on compile-time reflection. This is because the design of compile-time reflection features will likely influence the requirements for run-time reflection features.

Document number: N3810

Date: 2013-10-13

Alternatives for Array Extensions

by Bjarne Stroustrup

The most important aspect of an “array alternative” is that it enables simple and efficient use of a run-time-specified amount of stack storage and provides an alternative to the traditional problems of “lost” size and “lost” type that make direct use of arrays error-prone.

Here, I will record some reflections based on the array/dynarray discussions at the Chicago meeting with some brief analysis of the alternatives as a start of a discussion. I consider a resolution urgently needed. We need arrays with run-time-specified bounds and safer access to such storage “yesterday.”

Document number: N3806-08

Date: 2013-10-14

C++ Standard Core Language Active Issues, Revision 86

C++ Standard Core Language Defect Reports and Accepted Issues, Revision 86

C++ Standard Core Language Closed Issues, Revision 86

by William M. Miller

... a group of related documents that together describe the issues that have been raised regarding the C++ Standard.

Document number: N3801

Date: 2013-10-14

Removing Undefined Behavior from the Preprocessor

by Gabriel Dos Reis

This paper recommends removal of undefined behavior from the C++ preprocessor. In all cases, the erroneous constructs are identified as violations of diagnosable rules.