CppCon 2018: Jason Turner “Applied Best Practices”

—
—
What happens when we start a project from scratch and try to apply all of the best practices? How well do constexpr, noexcept, [[nodiscard]] and other features interact with each other? Is it possible to apply all of the best practices at once, or will they conflict with each other? We will explore current best practices and examine their impact on compile time, runtime and testing. We'll also see some of the unexpected effects that result when best practices are applied to a new project.
—
Jason Turner, Developer, Trainer, Speaker

I'm available for contracting and onsite training.
—
*-----*

[treyquattro]

Jason is really a great communicator, and C++ expert. I must catch one of these talks live soon.

[pocsbe]

"What feature to remove from C++ if you could? Implicit conversions!" Finally! Good to see I'm not alone with this observation.

[TheLeontheking]

love how he engages with the audience!

[philmarsh]

"portability is the best practice" Amen. I just wish more developers heeded this. The best code is portable. Period.

[minciNashu]

17:00 if readability is an issue, instead of trailing return types, you can break before function name. It's a style available in clang-format also. eg
[[nodiscard]] constexpr int
myGettter() const noexcept;

[Trassr]

Let's hope the implicit constexpr proposal makes it through.

[zaooo]

Thanks a lot for considering the non-local audience when doing audience polls.
There's nothing more aggravating than watching a talk where the presenter skips over something because the locals grok it when it can be key to a remote person's understanding.

[OperationDarkside]

Very entertaining. It's really interesting/annoying, that not everything is constexpr yet. A constexpr vector would be really nice.
If my employer would use C++, I would advise to book you. Even if it's just for fun.

[snow]

note 26:50: You can't actually declare a lambda to be nodiscard.

[EmmanuelNebula]

What debugger or IDE is he using? 36:12

[SciDiFuoco]

37:10 who thought that was a good idea

[JamesJones-iuey]

I'm not smart enough for this language. If I was writing an emulator I doubt I'd spend this much time obfuscating my code with the latest attributes and keywords just for the sake of it. I put a high value on readability and simplicity and I value my time. When it takes more than 100 columns and multiple keywords to write a correct method signature it's a sign you should take your language back to the drawing board. Nobody coming from another language is going to have a clue what is going on in c++ land and typing code should be one of the more trivial aspects of solving actual engineering problems. These cppcon talks feel short on motivating examples and tall on esoteric, introspective, snazzy new features. Which sucks because I want to be a better programmer in a pragmatic sense not just a guru.

[max_ishere]

Something that sounds easy but actually isn't. Sounds like conning yourself into something dangerously long.