Back to Basics: Templates in C++ - Nicolai Josuttis - CppCon 2022

[@thestarinthesky_]

Thanks CppCon for uploading videos here. so much appreciate it. Couldn't be more proud of this great community.

[@moderncpp]

Great talk. I believe that understanding templates reveals most of the C++ programming language.

[@parthapratimmukherjee]

Its amazing how Nico can make extremely complex topics approachable. I bought all his books!

[@thestarinthesky_]

You're brilliant! I LOVE your amazing books and you're my role model. Thanks for contributing to the world of C++

[@superscatboy]

Nico is a great speaker, I've been looking forward to this one!

[@wigglyk2796]

Wow the master himself. His book on templates is excellent. Thanks for this video.

[@CppCon]

Glad to hear that you enjoyed this presentation!

[@deadbird99]

Hands down the best templates course I've ever had. Thanks!!

[@OptimusVlad]

Wow, this is trippy. Didn't know this was a thing: if constexpr (requires {coll.push_back(val);})

[@prafulsrivastava7684]

This is exactly what I was looking for! Great talk!

[@the_real_foamidable]

Very cool talk. Always good to recapitulate the basics - there are to many things we use without understanding the underlying tech and history. BTW: Where can I get this awesome T-Shirt?

[@MyLucjusz]

That's a pure pleasure to listen to the prelection like this. Thank you!

[@stevea.b.9282]

Fantastic talk, thank you, I'm just starting to learn templates and this helped immensely, many thanks.

[@brandonz6121]

A truly insightful talk!

[@dark808bb8]

We need an "if compiles{" expression that takes the first branch if the code in that branch compiles 😅

[@chudchadanstud]

The much needed. We need better metaprogramming.

[@sky_is_the_limit_13]

Great talks! I love your books! You're absolutely amazing. BTW, I am looking for "Back to Basics 2022" playlist but couldn't find it.

[@richardvonlehe4581]

Well done! Engaging throughout.

[@Tony-tu8uz]

Very good! Thank you for the talk!

[@flocela]

thank you. even better the second time around! : )

[@xFabi99]

Templates are pretty awesome now, as is this talk ;)

[@xudongsun]

love his tshirt. where can I get one?

[@MalcolmParsons]

35:46 std::complex is only specified for float, double and long double, not for int.

[@yowadup1000]

Looks pretty exciting!

[@NickEnchev]

Excellent talk, thank you.

[@paulselormey7862]

Josuttis, thank you.

[@mahdies56]

Great talk

[@viacheslav1392]

Great talk man!

[@ssmondal007]

Super Sir, impressed :)

[@bareminimum-mrtz]

Thankyou so much !!

[@sanjaygatne1424]

nice talk. i had one query on slide no.31, why recursive call to "if" statement when you know number of var args. why not "range for".

[@thepiratepeter4630]

You can't iterate on an argument pack like you would do with a container, because the types of the various elements could be different.

[@thepiratepeter4630]

In his specific example you could avoid recursion using a fold expression.

[@atib1980]

There isn't a foreach construct in C++ that would allow you to loop through a range of data of different data types at runtime. C++ foreach works on only those data types that have implemented the basic input iterator related operators defined by the requirements of input iterators (begin(), end() operator++() and operator*). In the example on slide 31 you just want to print every fn argument on a separate line (where fn argument is of a certain type for which ostream& operator

[@Jam18123]

Very useful

[@ZackDia-Ptr]

Good stuff...

[@djupstaten2328]

This is why a TypeEval function is screaming to be created. I am 100% certain the std::people can create a better one than I can. Typeid() doesn't actually consider a tuple of string/int/string the same type as a tuple of variant/variant/map as the same types so there is no secure way to funnel them into whatever place or process they need to be. A bool function is totally fine as long as it is general (i.e. one container type instance should match with another, and with its type-name, regardless of their particular flavor of chaos inside). Knowing everything at compile time is neither realistic nor creatively workable. "Strongly typed" needs to not just be a begrudging neurosis or a religious mantra but also lead to supplying the proper tools for the coder to secure this strength on his or her end.

[@gnerkus]

Interesting talk, though not as 'basic' as I assumed. It would have been helpful if the speech bubbles were removed; the code in the speech bubbles could have been placed side-by-side with the code on the left. For example, at 4:18, the text in the speech bubble could have been replaced with the code on the left but with "T" and "typename" swapped out for "CustomType" and "class". The explanation need not change. 4:16 "...use a better name, like CustomType as shown in the example on the right". 3:37 "...can be replaced by class, as you can see in the example on the right..." Edit: I just noticed the speech bubbles do help as annotations in other slides.

[@BiddutMitra]

C with better structure, which is c++.

[@paulchamberlain7942]

pReality = (UnconditionalSurrender *)pVictoryPlan;

[@vasylvoina6663]

I call function templates for 145 000 different types, so I end up with 145 000 functions generated. Wow, really nice feature.

[@yseeme]

Keep C++ away from stupid politics

[@__hannibaalbarca__]

_CppCon_ please keep politic out.

[@toxic_champ]

they can't, there is "con" in channel's title. So following the agenda is what they have to do

[@rahulc480]

Just to understand, what are you talking about