Back to Basics: Smart Pointers - Rainer Grimm - CppCon 2020

[@MasteringCodeInterviews]

The most invaluable resource to learn c++.It clarifies all the doubts of smart pointer.Rainer thanks a lot for such in depth talk.

[@MicheleTurchiarelli]

Love the CppCon. It's always a pleasure to watch, even for those things that I already know and studied.

[@JeremyCoppin]

Thanks. Brilliant and long overdue. All other talks on this subject ( and I have watched hours) have always left me with more questions than answers esp wrt using smart pointers in function calls.

[@jvsnyc]

Yeah. Some may be hand-waving saying that they should always be encapsulated in some other object, but really don't focus on it at all.

[@myown236]

What an excellent presentation. Suchba rare and clear wisdom on smart pointers.

[@PepeOsca]

Oh God, this talk is gold! Thanks Rainer.

[@hanyanglee9018]

unique pointers are very special. Generally don't put them in any std container unless you know what you are doing. I remember I saw the idea again and again that if something is not copy-able and the copied version is equivalent to the origin version and the original one is not modified, it's not an element for you to put into std containers. Unique point is the most famous one in such cases. But if you limit the manipulation like: no copy at all, like a vector and only emplace_back(or push_back(std::move(...)) just like what you see in the video) and never modify it, it maybe ok.

[@jvsnyc]

Some people like to say that we called it RAII because RFID was already taken for another meaning (Radio Frequency Id)....but Resource Freeing Is Destruction would be more apt otherwise.

[@MikePrice888]

such a good presentation with plenty of examples for different levels! thank you so much

[@CppCon]

Glad it was helpful!

[@hanyanglee9018]

1:02:54 I don't agree with you professor. In this case, a weak pointer maybe the best. Usually in such cases, there is a tree like memory management under the hood. It's syntaxly a pointer but in fact a handle. It's not designed to be deleted by user. Usually the library also provides a destroy-like function to determine the object and this is always shown in docs. Shouldn't be a problem.

[@yjc149]

another greate back to basic video !

[@jvsnyc]

This seems to go the furthest of any of the "short" one hour talks about best practices when pointers and references appear in function parameter lists. Near the end ~54:00

[@hanyanglee9018]

We will only see the destructor of daughter when the family goes out of scope. What a sad story.

[@konstantinburlachenko2843]

Small mistake at slide 11 there is also a weak pointer counter inside shared pointer control block

[@thorsten9211]

Helped me a lot to understand shared_ptr`s :) Thanks!

[@retrom]

Pumped for this one.

[@maciejurbanski6206]

Thank you a lot for useful knowledge!

[@CppCon]

Glad it was helpful!

[@retropaganda8442]

Thank you for using KDE.

[@Fetrovsky]

In my overview, I give an overview of what my overview is.

[@__hannibaalbarca__]

Best : oh this a terrible English i can’t read it; this what happened to me 15 years before and waist too much time for English grammer and listen