CppCon 2018: “Grill the Committee”

—
—
What would you like to know about the C++ standard?

Join us for a panel discussion with the leaders of the C++ standards committee where the audience asks the questions.
—
Jon Kalb, Jon Kalb, Consulting
Conference Chair
Jon Kalb is a freelance C++ instructor and chairs CppCon, C++ Now, and the Boost Steering Committee. He is a director and the treasurer of the C++ Alliance.
He has been programming in C++ for over 25 years and has written C++ for Amazon, Apple, Dow Chemical, Intuit, Lotus, Microsoft, Netscape, Sun, and Yahoo!

Marshall Clow, Qualcomm
Marshall has been programming professionally for 35 yearsHe is the author of Boost.Algorithm, and has been a contributor to Boost for more than 15 years. He is the chairman of the Library working group of the C++ standard committee. He is the lead developer for libc++, the C++ standard library for LLVM.

Olivier Giroux, NVIDIA
Olivier Giroux has worked on nine GPU and five SM architecture generations released by NVIDIA. Lately, he works to clarify the forms and semantics of valid GPU programs, present and future. He was the programming model lead for the NVIDIA Volta architecture. He is the chair of SG1, the Concurrency study group of the ISO C++ committee, and is a passionate contributor to C++'s forward progress guarantees and memory model.

Howard Hinnant
Ripple

Bjarne Stroustrup, MorganStanley
dization, future; performance, reliability; software developer education;

Herb Sutter, Microsoft
Author, and chair of the ISO C++ committee.

Ville Voutilainen, Qt Company
Ville Voutilainen is the Chair of the Evolution Working Group, and also a gcc/libstdc++ developer. He's the Finnish representative in the C++ committee, and has contributed to numerous C++11 and C++14 facilities, including override/final, lambda init-captures, aggregate NSDMIs, and more.

Titus Winters, Google
C++ Codebase Cultivator
Titus Winters has spent the past 6 years working on Google's core C++ libraries. He's particularly interested in issues of large scale software engineer and codebase maintenance: how do we keep a codebase of over 100M lines of code consistent and flexible for the next decade? Along the way he has helped Google teams pioneer techniques to perform automated code transformations on a massive scale, and helps maintain the Google C++ Style Guide.
—

*-----*
*-----*

[shahmiBro]

I like Howard Hinnant's style, he just calm & cool, letting others doing the ceaseless blabla.... Long live chrono;

[Voy]

omg, question about cammel case... if you want to hang out with Bjarne ask him out for a diner, do not waste time of hundreds of people in the audience and on YT

[OperationDarkside]

I don't know if this is already in place, but how about official community votings on features/TSs?
Just for the committee to get a feel for the user base. So net everyone has to be part of the committee or a subgroup, but can have voice.

[allopeth]

Marshall Clow reminds me of some actor but I cannot quite remember who that is?

[LemonChieff]

I mostly use `auto` for ranged for loop just because it's such an idiom. `for (auto& foo` you know what's coming…
`for (int i`do you really expect `for (int i: foo)` ? I don't.
For templates of course I often use auto or if the type/class name is long and appears on the right-hand side anyway, ie:
now = What's the name of the variable?
Let me help: `auto now =

There are use cases. You're taking it WAY TOO FUCKING FAR if you have:
`auto main() -> int` NO. Just NO.