QuoteOriginally posted by: CuchulainnBig shame that C++ does not supportinterfaceconcepts/contractsC++17 -- or a TS around 2017 -- just might :-)More:Trip report: Fall 2015 ISO C++ standards meetinghttp://herbsutter.com/2015/10/25/2568/QuoteConcepts TS: It's published! We did that between meetings, but it's worth mentioning again here. There was initial discussion about putting it directly into C++17; we expect to seriously consider that at our next meeting.. . . Modules has reached a milestone: design agreement! This was done by separating "phase 1" and "phase 2" of modules, and greenlighting phase 1 to proceed to wordsmithing for adoption (hopefully at our next meeting) into a new Modules TS, while in parallel continuing work on an expanded phase 2 which can follow.. . .Contracts seem to have made a breakthrough in getting the various parties to agree on the nitty-gritty details of a design. This consumed two three-hour evening sessions on Tuesday and Wednesday nights. If this holds, we expect to see a combined proposal that for the first time achieves broad agreement in time for our next meeting.CppCon 2015: Gabriel Dos Reis "Contracts for Dependable C++"
of the three major areas that C++17 is expected to address is "improving support for large-scale dependable software." A general understanding of "dependable software" is the notion that the product should reliably perform the task it was designed for, and when given erroneous inputs the program should not be allowed to blindly continue execution, thereby possibly causing serious harms. In another words, an abrupt program termination is preferable to an exploited program vulnerability."Contracts" are a language feature being considered by the ISO C++ standards committee for C++17. They offer a basic mitigation measure, and early containment mechanism, by allowing a C++ programmer express more formally (instead of just comments) in code the requirements of a function interface. They offer a complement to conventional static type checking, and move comments closer to mechanized scrutiny. This presentation will explore the design space, previous efforts, the importance of analysis tools (both static and dynamic), and how contracts provide greater integration and support.CppCon 2015: Gabriel Dos Reis "Large Scale C++ with Modules: What You Should Know"
" are a frequently requested and long-awaited feature by C++ programmers. In a nutshell, the idea is to have a direct language support for (a) expressing the boundaries and dependencies of a program component; (b) isolating source codes from macro vagaries; (c) scaling compile time, especially for large projects, given the ubiquity of "headers-only" template libraries; (d) spur innovation and deployment of semantics-aware developer tools.This presentation will focus on three major points: (1) the design of the module proposal currently being considered by the C++ standards committee (design goals, properties, constraints); (2) implementations currently under way; and (3) early user experience and migration.Modules directly address a problem (scalability) listed as one of the three major areas where C++17 is expected to significantly improve daily experience of the working C++ programmer. Naturally, this feature is also on the top ten list of C++17 functionalities Bjarne Stroustrup put forward in his "Thought on C++17."