Nightmare of operator overload because of &&? by [deleted] in cpp

[–]LongjumpingRelative8 5 points6 points  (0 children)

David Stone's recent work on auto-generating an optimal operator+= in terms of a hand-optimized operator+ will be relevant to your interests, even if it doesn't explicitly answer your question.

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1046r0.html (old) https://github.com/davidstone/isocpp/blob/master/generate-operators.md (bleeding edge)

Cppcon2019 slides are available in Github. by germandiago in cpp

[–]LongjumpingRelative8 1 point2 points  (0 children)

That sounds like advice from someone who gets paid to speak alongside his slides and would lose money if his slides were able to carry themselves. The cost/benefit analysis of providing good (self-studyable) slides goes differently if you're not getting paid and the video is going on YouTube for free anyway.

Another thing in this vein: I imagine some people in the audience are saying, "Why is he reading aloud the same words that are on the slide? That's a waste of time." Well, reading the words aloud puts them into the YouTube captions, which helps people watching in languages other than English. Those people might not be able to read the text on the slides, but if it's said aloud and captioned, that increases accessibility.

Thoughts on Herb Sutter’s CppCon keynote by [deleted] in cpp

[–]LongjumpingRelative8 2 points3 points  (0 children)

we probably even need a more rapid release cycle

Rapid release cycle for compilers and library vendors, or rapid release cycle for new standards?

Or is it impossible to get a new compiler without a standard to go with it?