Standardization

ISO C++ Committee – Jacksonville 2018, trip report -- Timur Doumler

Timur Doumler has joined the CLion team in fall 2017. He continues to be active on the C++ Committee, as it fits well into JetBrains' strategy: our C++ team would like to be actively involved in the committee and feed our experience with implementing language features in our C++ tools back into the ongoing work on the evolution of the C++ language.

ISO C++ Committee – Jacksonville 2018 trip report

by Timur Doumler

From the article:

From the 12th to the 17th of March 2018, I travelled to Jacksonville, Florida, to attend the ISO C++ Committee meeting as JetBrains’ representative on the committee. I decided to focus on Evolution Working Group and cover the most relevant discussions concerning language evolution:

  • Day 1: Structured bindings and concepts
  • Day 2: Let’s break some code!
  • Day 3: Coroutines and Modules
  • Day 4: Compile-time programming
  • Day 5: New Tooling Study Group
  • Day 6: Plenary

Dependency Management For C++ -- Hans Klabbers

Dependency management is a missing piece in the C++ eco system.

Dependency Management For C++

by Hans Klabbers

About the article

The writer took part in the developer survey and followed up on the outcome. Depenendency management is seen as a missing piece in the C++ standard. The article is written as a response on a tweet by Bryce Lelbach and an article on medium by Corentin. It describes the author's ideas for dependency management. 

trip report: first ISO C++ meeting experience -- Vittorio Romeo

This trip report covers the author's first ISO C++ meeting experience. Vittorio talks about the most interesting interactions and papers discussed in Jacksonville, while also sharing some of his thoughts regarding controversial topics such as modules and 2D graphics.

trip report: first ISO C++ meeting experience

By Vittorio Romeo

From the article:

I'm back in London from Jacksonville, where I attended my first ISO C++ meeting. Apart from the long flights and long working hours, it has been a very enjoyable experience for multiple reasons: [...]

[...] almost every interaction when debating a paper was very well motivated, and I found myself thinking "that's a very good point" very often, even when two conflicting opinions were being stated one right after the other [...]

Guy Davidson's Jacksonville Trip Report

Having landed safely in Britain and recovered somewhat from his mystery illness, Guy has prepared a trip report, paying particular attention to the drama of the 2D Graphics paper and the unexpected interruption to the closing plenary.

Oh, lock-free circular buffers, yay! Hey, no 2D graphics? Jacksonville trip report

by Guy Davidson

From the article:

Right now, both library groups are processing fewer papers than they receive. There are 19 sessions of about two hours during each meeting, and LWG spent the first five sessions on P0214, Data-Parallel Vector Types & Operations (for the Parallelism TS), which defines some SIMD types. I was delighted to be in on this, and even offered to scribe but found it impossibly hard, unlike my stint in LEWG at Toronto. However, it was during the fourth of these sessions that I started to feel distinctly unwell.

Text Formatting at the ISO C++ standards meeting in Jacksonville--Victor Zverovich

A good library fro formatting in the standard, soon?

Text Formatting at the ISO C++ standards meeting in Jacksonville

by Victor Zverovich

From the article:

This week I attended the ISO C++ standards committee meeting to present the second revision of my paper P0645R1 Text Formatting, based on the {fmt} formatting library. The first revision was reviewed by Library Evolution Working Group (LEWG) in June 2017 in Toronto and there was a lot of feedback, particularly I’ve been asked to

  • investigate compile-time format string processing,
  • look at using or explain why not to use an output iterator,
  • use string_view,
  • allow pre-computation of output size,
  • add benchmarks.

It took me a while to address all the feedback, especially the first two items which required substantial API and implementation changes, so I had to skip the meeting in Albuquerque. However, this ultimately resulted in a much better API so I’m grateful to LEWG for the helpful guidance. Despite all the negative press covfefe “design by committee” sometimes works surprisingly well...

Results summary: C++ Foundation Developer Survey "Lite", 2018-02

From last Monday through this Monday, we ran our first global C++ developer survey.

Thank you to the over 3,200 of you who responded. As promised, here is a public summary of the results:

Results summary: C++ Developer Survey "Lite": 2018-02

This summary has now been forwarded to the C++ standards committee, along with the full text of your write-in answers (over 300 pages!). Your feedback will be very helpful, and has already started to be referred to by standards participants as we prepare for next week's ISO meeting in Jacksonville, FL, USA.

Thank you again for your participation. It is very helpful, and based on the success of this survey we plan to run it again in the future from time to time. When we do, it will be announced here on isocpp.org.

 

Note: Due to a SurveyMonkey bug, the word clouds showing popular keywords for the five open-ended questions cover about half the responses, which fortunately is still a large sample. They're working on a fix to include all the responses in the word clouds.

New: C++ Foundation Developer Survey "Lite", 2018-02

cpp_logo.pngToday the Standard C++ Foundation opened its first-ever global C++ developer survey. As the name suggests, it's a one-pager:

C++ Developer Survey "Lite": 2018-02

Please take 10 minutes or so to participate! A summary of the results, including aggregated highlights of common answers in the write-in responses, will be posted publicly here on isocpp.org and shared with the C++ standardization committee to help inform C++ evolution.

If this one is successful we plan to do it again, perhaps annually or quarterly.

Thank you for participating and helping to inform our committee and community.

Batteries not included: what should go in the C++ standard library?

With the next standardisation meeting coming up, now is a good time to consider what the limits of the standard library should be. 

Batteries not included: what should go in the C++ standard library?

By Guy Davidson

From the article:

About forty Christmases ago I was absolutely delighted to open a slot car racing set from my parents. I feverishly set everything up, created a track reminiscent of Brands Hatch, and went to plug everything in, only to discover that I needed batteries to operate the controllers. This was Great Britain in the 1970s...