October 2013

N3787: What can signal handlers do? (CWG 1441) -- Hans Boehm

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: N3787

Date: 2013-10-14

What can signal handlers do? (CWG 1441)

by Hans Boehm

Excerpt:

This is an attempt to summarize the current state of discussions around CWG issue 1441. Much of this discussion has occurred within SG1, and it has moved significantly past the original issue, so it seemed appropriate to turn it into a separate paper. This attempts to reflect the contributions of many people, especially Lawrence Crowl, Jens Maurer, Clark Nelson, and Detlef Vollmann.

This version is a minor revision of N3633. It reflects some changes due to SG1 concerns in Chicago, and reflects the easiest-to-address comments from the CWG discussion in Chicago. It does not reflect all of the latter. More discussion and almost certainly another paper revision is required.

N3785: Executors and schedulers, revision 3 -- C Mysen, N Gustafsson, M Austern, J Yasskin

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: N3785

Date: 2013-10-08

Executors and schedulers, revision 3

by Chris Mysen, Niklas Gustafsson, Matt Austern, Jeffrey Yasskin

Excerpt:

This paper is a proposal for executors, objects that can execute units of work packaged as
function objects, in the form of an abstract base class and several concrete classes that
inherit from it. It is based on components that are heavily used in internal Google and
Microsoft code, with changes to better match the style of the C++ standard.

This proposal discusses the design decisions behind the API and also includes a first draft of
formal wording for the working paper.

N3784: Improvements to std::future and Related APIs -- Gustafsson, Laksberg, Sutter, Mithani

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: N3784

Date: 2013-09-27

Improvements to std::future and Related APIs

by Niklas Gustafsson, Artur Laksberg, Herb Sutter, Sana Mithani

Excerpt:

This proposal is an evolution of the functionality of std::future/std::shared_future. It details additions which can enable wait free compositions of asynchronous operations.

This document supersedes N3634: the title has been changed, and the proposed changes have been modified to be expressed as edits to the C++ Draft Standard.

New in this version: implicit unwrapping (one level) of future<future<R>> to future<R> in then().

N3782: Index Based Ranges (Rev. 1) -- Arno Schödl, Fabio Fracassi

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: N3782

Date: 2013-09-24

Index Based Ranges (Rev. 1)

by Arno Schödl, Fabio Fracassi

Excerpt:

Key Points

In contrast to most currently popular range implementations, which define range iterations in terms of (pairs of) iterators we propose to use range adaptors and indices (which is similar to N1873 - Cursor/Property Maps). The most important consequence of this is that we can avoid ”Fat Iterators” when stacking range adaptors, in particular range filters.

Ranges and Traversables

This paper is intended to be fully compatible with N3763 - Traversable Arguments. We intedend to use the Traversable concept as a basis wherever applicable. N3763 sets a good foundation for making Traversables easy to work with. In this paper we would like to explore the design space beyond this basis to make working with them both easy and powerful for programmers.

N3780: Why Deprecating async() Is the Worst of All Options -- Nicolai Josuttis

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: N3780

Date: 2013-109-26

Why Deprecating async() Is the Worst of All Options

by Nicolai Josuttis

Note: This was an intra-meeting paper in Chicago, and std::async was not deprecated.

N3772: Changing the type of address-of-member expression -- David Rodríguez Ibeas

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: N3772

Date: 2013-09-05

Changing the type of address-of-member expression

by David Rodriguez Ibeas

Excerpt:

This proposal addresses the same issue as CWG closed issue 203 "Type of address-ofmember" by providing a broader view of the issue and the implications that it has on other parts of the C++ standard.

N3770: C++ CD Comment Status, Rev. 1 -- Miller, Meredith

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: N3770

Date: 2013-10-14

C++ CD Comment Status, Rev. 1

by William M. Miller, Alisdair Meredith

Excerpt:

This document summarizes the status of WG21 following the 2013-09 (Chicago) meeting in addressing National Body comments on Committee Draft document N3690. It does not contain the results of the Library Working Group deliberations, which have not yet been fully processed.

N3768: WG21 Minutes (September 2013), Chicago IL USA -- Kyle Kloepper

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: N3768

Date: 2013-10-16

Minutes (September 2013): PL22.16 Meeting No. 61, WG21 Meeting No. 56, 23-28 September 2013, Chicago, Illinois, USA

by Kyle Kloepper

 

C++11 and Boost

What issues arise when combining C++11 and (older) Boost code that has pre-standard versions of C++11 features?

C++11 and Boost

by Jens Weller

From the article:

Some parts of the Standard Library in C++11 are predated in boost. When playing around with C++11, you get used to using some parts in the Standard Library that are used in C++03 with their boost counterpart. Also, there is some libraries now occuring, which are C++11 based, so interfacing with either boost or C++11 code is soon an issue.

N3820: Working Draft, Technical Specification -- Array Extensions -- Lawrence Crowl

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: N3820

Date: 2013-10-10

Working Draft, Technical Specification — Array Extensions

by Lawrence Crowl

Excerpt:

This Technical Specification specifies requirements for implementations of various extensions for arrays to the C++ language and library. Included are:

arrays of runtime bound: The core language is extended to permit run-time computation of the bound of an array with automatic  storage duration.

class dynarray: The library is extended with a class that specifies an array size only on construction.