Note: This is the last batch of individually- or small-group-posted papers this week. Tomorrow is the pre-Jacksonville paper mailing deadline, so we expect a bunch of papers to come in all at once, and instead of blogging about them individually, those will all advertised here next week as part of the mailing blog post.
New WG21 papers are available. If you are not a committee member, please use the comments section below or the std-proposals forum for public discussion.
P0186R0: Iterator Facade Library Proposal for Ranges (Beman Dawes, Eric Niebler, Casey Carter)
Proposes a library component for easily creating conforming iterators. Based on existing practice. Depends only on the C++17 working paper plus Concepts TS and Ranges TS. Breaks no existing code or ABI's. Two open-source implementations including test suites available. Proposed wording provided.
P0218R0: Adopt the File System TS for C++17 (Beman Dawes)
Technical work on N4100, File System Technical Specification, ISO/IEC TS 18822:2015, was completed in July 2014, and published by ISO in July 2015. There are three shipping implementations and one soon-to-ship implementation. Two of the shipping implementations have been have been in use for several years. This document proposes adopting the File System Technical Specification, with corrections, for C++17. The alternative to this proposal is to start work on version two of the File System TS. Doing nothing is not an alternative.
P0251R0: Unified Call Syntax Wording (Bjarne Stroustrup, Herb Sutter)
This is the proposed wording for a unified call syntax based on the idea that
f(x,y)can invoke a member function,
x.f(y), if there are no
f(x,y). The inverse transformation, from
f(x,y)is not proposed. [...] As agreed in EWG at the Kona meeting, the intent of the wording is: For
f(x,y), see if
f(x,y)is valid and if so do that call; otherwise try