Smart Pointers in C++ (Stop Using new?)

[@codebreakthrough]

I hope this was helpful! Here is the course link I mentioned in the video. New C/C++ course: calcur.tech/c-cpp-newsletter

[@vinniciusrosa8284]

I do not know yet how to pass unique_ptr as reference to a function. void whatever(...,std::unique_ptr &engine); - - - The call: whatever(engine). It should work, but do not compile.

[@andreasguettinger6706]

As somebody who learned and uses mainly C++98, I'm glad to see videos about these newer C++ concepts I often forget about. 👍

[@Nathan00at78Uuiu]

let's go. This is what we need. Been using your lessons for learning anything. So far been great. thanks.

[@agailloty]

I have never coded in C++ but lately I started learning Rust, while watching this video I can understand why the ownership/borrow model is powerful paradigm to enforce memory safety. It seems so easy to create bugs in C++

[@billbez7465]

Very well done. There were other videos on smart pointers that left me a bit confused. Yours is clear & understandable. Thank you

[@lilyscarlet2584]

handmade hero is a great series on youtube. it uses c++ to make a game from scratch and teaches how to properly manage memory etc. it starts with the windows platform layer and how to do cross platform proper.

[@aminramazanifar9743]

As great as always. Cannot wait to see the course. Thanks!

[@OlliS71]

shared_ptr is for sharing between threads, i.e. when handling shared data to another thread. Within a thread it's too slow because the control-block is atomically updated.

[@sebastianroubert7543]

You’re a beast. Been watching for interview prep. You should start an udemy course!

[@suryadon947]

Best video for smart pointers Great bro🎉

[@MichaelCohen-sb7tw]

Thanks Caleb. Very clear examples and explanations.

[@xbiohazardx7312]

This video is very helpful, it's make me figured it out in one video huge thanks!

[@skauddy755]

Very clear explanation

[@Sluggernaut]

11:27 cracked up so hard. I do this all of the time when making videos. Edit: wth? How did that even compile at 13:12. You have to declare the data type when making a shared pointer. Weird.

[@michaeldamolsen]

"How did that even compile at 13:12. You have to declare the data type when making a shared pointer." - Since C++ 17 there are deduction guides which allow weak_ptr to take over the type from the shared_ptr and the other way around.

[@abhishekkhanchi9105]

Hi Caleb i ran shared pointer example.its giving error . error:smart_p3.cpp:6:34: error: conversion from ‘’ to non-scalar type ‘std::shared_ptr’ requested 6 | std::shared_ptr a= std::make_shared; during compilation . which c++ compiler ur using.. I tried this on g++: gcc version 9.4.0 Please guide Thanks Abhishek

[@codebreakthrough]

You have it should be (5) It looks like it thinks you are trying to use a function for the type because you put the () inside the

[@abhishekkhanchi9105]

thanks alot caleb(@@codebreakthrough ) it work for me..

[@Aragon947]

but for a big game loop i would avoid smart pointers because there are slower?

[@ArtVandelayInc]

Great tutorial! Thank you

[@dwivedys]

Hey good presentation Caleb!

[@古川範和]

This is one of the best coding tutorial videos I've watched. Clear, concise and complete. Thank you so much for your great work!

[@fpldaily5172]

hey bro. Please do a java springboot video or course?

[@alirezaarttam3344]

Awsome. Thanks!

[@midewestmond9442]

Why you using camel case btw and more can you make a video how to setup an editor for c++ development

[@tylerbakeman]

new and delete are fine. smart pointers can do things automatically with slight overhead. the overhead is insignificant, but so is managing new and delete...

[@NoSpeechForTheDumb]

As a user, you shouldn't be using new/delete anymore. As a library developer, you need it to implement RAII.

[@Brad_Script]

what I find weird about this code is that you are allowed to return a unique_ptr from a function without using the move function. Is seems that the compiler is smart enough to realize you are moving the unique_ptr from the function to the caller of the function.

[@nokia_n-gage]

Thanks!

[@panjak323]

The level of abstraction is on a really akward level. On one hand yeey nice, you don't have to delete pointers manually. On the other hand, if you need to do anything more advanced like cloning, deep and or shallow copy and storing in containers, that requires even more work, knowledge and frustration than managing raw memory directly. I find using smart pointers in very simple situations, where it's not necessary at all and in complicated situations I use raw pointers, just because I hate thinking about the obscure behavior of smart pointers.

[@snesmocha]

Isn’t that what smart pointers?

[@KaiDevvy]

Smart pointers are a fairly thin wrapper in terms of added complexity. It's not a huge difference in understanding to use them as opposed to raw pointers, and the benefits of clearly defined ownership and automatic deallocation is monumental for the little abstraction. To me though, something that bothers me is just how verbose it is. Going from * to std::shared_ptr is a pain in the ass. Especially when you're making collections of smart pointers or the like

[@赛尼木]

cystall clear!

[@hiankun]

Ownership, lifetime,... After learning some basic Rust, all of these make sense. 😀🦀

[@CCCole1]

P.S. Love the content

[@sent4dc]

4:39 WRONG! 2 memory leaks.

[@hawks3109]

Don't use auto in production code, the rest is good, but auto can make bad assumptions when you start getting into nested data types and other techniques that come up in production code. auto is dangerous and could lead to bad assumptions by the compiler.

[@y_x2]

Absolutely ridiculous... simply put variable a outside main!

[@zohnannor]

bro thinks hes mcoding💀💀