CppCon 2017: Panel “Grill the Committee”

preview_player
Показать описание


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.

This we've got the the chairs of the Core Evolution and Language Evolution working groups, joined by the primary authors of such major upcoming features as concepts, metaclasses, ranges, modules, coroutines, compile time programming, and the spaceship operator.

Moderator: Jon Kalb
Panel: Louis Dionne, Eric Niebler, Gor Nishanov, Gabriel Dos Reis, Bjarne Stroustrup, Herb Sutter, Andrew Sutton, Ville Voutilainen, Titus Winters


*-----*
*-----*
Рекомендации по теме
Комментарии
Автор

The fact that a some simple questions spark a 5 to 10 minute answer/discussion says something about the complexity and difficulty the committee has to deal with.

psyrz
Автор

I think the frequent comparison to python's troubles with v2 v3 is erroneous, as python is interpreted and the interpreters installed on the end user machine must match the source code. This is not an issue with languages compiled to binary instructions, either old code can be compiled with specific compiler versions or a compiler flag can be set to the desired standard. The end user of a binary package is not concerned with the compiler version used(likely they don't even care about the general source language as long as the binary is fast enough and not full of bugs.) The only significant issue may be some libraries that are using tidbits that would be deprecated in the new version.(but shouldn't they be updated to more desired code either way?) This library issue could even be addressed between compile and linking because separate files can use different compiler flags and the link stage works with assembled instructions in any case so shouldn't be strongly effected. (in interpreted langs all the files must at run-time go through a single interpreter and use the same flags.)

Python also failed in v3.0 to require, or at least strongly suggest, that v3 interpreters be explicitly named and called as such in v3 source code. And so they ended up with both v2 and v3 interpreters use the generic name "python" on the host system and when called via #!/bin/python. Instead, v3 should have always been explicitly named "python3" [or "py3", an unambiguous name anyway].

TheDuckofDoom.
Автор

6:05 That's genuinely funny :D

Bjarne is a funny guy.

Dante
Автор

Titus sounds like he's about to explode.

origamibulldoser
Автор

Grill the committee panles should be at six hours long. At minimum.

kamilziemian
Автор

I really hoped at 50:40 he was going to say 'also...there are other ways to do that'

doms
Автор

33:30 Big plus to Stroustrup for mentioning Lisp

kamilziemian
Автор

Grill, grill, grill the committe! More, more and more, grill the committee!

kamilziemian
Автор

Where is the grill with the committee after work video ?

llothar
Автор

Hahaha... Impressing conversation, nice committee[ including more in the committee is better, because there are many qualified remained outside], again nice discussion. Actually, defending class [with proper explanation -"on demand"] is always acceptable, highly appreciable. #The problem is - you have no universal BENCHMARK[DATUM] of your STD[Actually Faulty] Library.

kamalabuhenamostafa
Автор

5 words definitely make things interesting

vetsebojs
Автор

1:06:05 "80% hate formatting using overloaded operator<<." What is so bad about it?

ARTijOMS
Автор

I'll only say one thing : Bjarne's right when he says TMP is being used for something it is not meant to do. Stop adding library features or ugly patches such as SFINAE. Don't add more glue to the glue, fix the problem, not the glue. templates are a tool, but not made for what we are doing with it today, please just stop.

Lectem
Автор

Modern C++ is almost not usable anymore. We want to solve problems by programming and don't have time to understand a 20 pages long template error message. So all new projects in our company are set up with Java. Even our firmware devolpers use C, because in their opinion, C++ has become an academic monster.

DrOggy
Автор

no female...
should I be triggered or something??



never mind..., ice cream's here

PoojaDeshpande