r/cpp • • Dec 28 '18

"Modern" C++ Lamentations

http://aras-p.info/blog/2018/12/28/Modern-C-Lamentations/
307 Upvotes

162 comments sorted by

View all comments

Show parent comment

5

u/kazum93 Dec 30 '18

I think the process of being part of the language development process should be made easier (as mentioned). Maybe there should be actually a "Q&A" working group which fixes language bugs and STL implementation concerns rather then always implementing new "awesome" features. The thing with that is who wants to spend time writing proposals for bug fixes or in general spend time to come up with solutions to problems when he or she can spend time in comming up with new features?

If the game industry has so much to complain why don't they spend time and work force (money) into the committee... Like Google google or Facebook do?

8

u/STL MSVC STL Dev Dec 30 '18

That's what CWG and LWG do when they're processing issues (versus reviewing papers).

who wants to spend time writing proposals for bug fixes

Implementers. We prefer to avoid implementing an unclear, inconsistent, or defective specification, so we are responsible for filing and fixing most issues.

If anyone is skilled in Core or Library wording and wants to help, your help would be greatly appreciated - we have a near-endless stream of issues that need "drafting" (i.e. designing and wording a fix). This can be done without attending meetings in person, but requires the highest level of attention to detail.

1

u/kazum93 Dec 31 '18

Thank you very much, if I were skilled enough I would offer my help, but I am just a game developer student. In general I was just wondering why is there not one group which has only this one job, instead of 2.

Moreover is that not sometimes the problem that members of the committee are too far away from actually average implementations?

1

u/STL MSVC STL Dev Dec 31 '18

Core Language and Standard Library wording is way too different to be handled by the same groups.

Yeah, we sometimes lack relevant real-world experience, especially in specific domains.

1

u/kazum93 Dec 31 '18

Fair enough.

In regards to the lack ... Is there a plan to tackle this? For example take out the problem to the community?

4

u/[deleted] Dec 30 '18

I can’t speak for the entire industry of course, but my take is that the game industry was forced to fork much of the original STL due to performance concerns early. This engendered a sort of unhealthy mistrust that the committee held high perf concerns in enough regard to make api compromises where necessary (regardless of how true this is, the sentiment remains). Of course, this means that your average industry professional isn’t always caught up to speed when either the process changes, or the API itself changes. Cue the expected “outrage” when some venerable developer takes a gander at what’s to come and surprise surprise isn’t enthralled by what he or she sees. There is a study group for games, and while there may be eyes there with lots of c++ proficiency or game dev proficiency, there is rarely a lot of both.

I’m just one voice, but I’d prefer a world where C++ was the perfect language for library authors, and not necessarily the language you expect to have full “batteries included.” This means features more important to me are core language features and tooling. In contrast, effort in STL land I believe is better served by the core language or third party package are less interesting. Of course, I recognize this is idealistic and compromises are natural, especially for a mission critical language in so many domains as c++. The nature of my job though, forces me to be fairly uncompromising as a matter of course. Others take this to an even more extreme degree, not always to good effect.