CppCon 2016: 'C++ Standard Library Panel'

—
—
Want to meet your standard library maintainer? Now's your chance! Join us for a panel discussion of the C++ standard library with the people who implement it! C++ standard library maintainers and members of the C++ Committee's Library Working Group will talk about the philosophy behind the specification and implementation of the C++ standard library. We'll talk about all the new library features coming in C++17 (and beyond).
—

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

[MaherBaba]

I salute all of this good men who work to make c++ great again

[paulhoad]

40:00 In response to a question from the floor, some operator overloads may seem odd at first glance but the operators like / and /= have some good usecases

e.g. for /= when you have something like a path class and your wanting to do

pathClass myPath = "/usr/local";
myPath /= "bin";
myPath /= "wget";

for operator / is obviously useful when your class models something that it makes sense to do a divide say TimeSpan type class and you want to overload / so that you can divide one TimeSpan by another i.e. how many 8 hour shifts are there in a given timespan

e.g. 36:20:40 / 8:00:00

How could we get rid of / and /= operators and not keep these perfectly valid usecases?

[llothar]

What is the kid from Bad Santa 2 doing on the stage ?

[timonpasslick]

In std2, please add container versions of your algorithms.

[TheDuckofDoom.]

The question near 36:30 about the "experimental" term, It seems to me that "testing" or similar would be more appropriate given the description of a late revision nearly standard ready.
My US-english speaking mind associates "experimental" with an explicitly non-production item, possibly in a state intended to discover the behavior of edge cases.

[Fetrovsky]

They keep saying STL. I think they're referring to "The C++ Standard Library", or portions of it that are implemented with templates.

[Silmarieni]

Is Alexander Stepanov involved in STL2 ?

[raghureddy]

I started working on C++, its gonna be good ofcourse! :P

[Orgyilkos]

Why not compiler directives like:
"using piped_streams;"? That won't break compatibility and you would not need to type weird stuffs either. I see that in the time of std2 a tool that allows std:: to be treated as std2:: when possible would *always* be used.

[Advanium]

59:00 this part is so true. The workflow in C++ can be really horrible, and a "proper" standard library should help the developer out. Not everyone knows how to create libraries or expert algorithms or do not have the manpower, but sure they would know how to use the tools at hand.

[Fetrovsky]

I kind of like stud better than stood. Still not too crazy about wanting to force std into a pronounceable word.