C++ 11: Rvalue Reference -- Move Semantics

Very nice explanation. Thanks.

No kidding, this is the first time this made perfect sense to me, thank you sir. I subscribed to your channel

Thank you! Great explanation!

Thanks a lot for such excellent content with a beautiful explanation. Kindly share other latest versions too.

excellent

Would be wonderful to upgrade this series to c++20

Thanks for this videos! Unitl now I was creating move constructors like it was alchemy

How does this syntax being ok? "rhs.arr_ = nullptr", while before hand the pointer "arr_ = rhs.arr" is pointing to it?

Compared to other C++ tutorials, this one clearly has the touch of a master.

Can anyone please explain me how constructor is calling with the function calling ?

This tutorial is fucking great.

Can we just acknowledge how much of a legend this guy is. These tutorials are honking good!

Great video

awesome video. I"ve been learning cpp b/c of the new work. And lots of nuances that I need to learn from a java background.

You sound like erchito

this video was an ablosute eye opener! thank you so much :)

With g++ passing a rvalue will perform a copy elision. So we need to disable copy elision in order to see a move constructor called.

great tutorial, very clearly illustrated, much better than many so called professor.

Clear and clean. Thank you!

Thank u for your clear explanation, it was very educational.

Thank god someone who explained the usage of move constructors without giving the example of push_back for vectors!

good video, very well explained

It's hard to talk about this when you can't pronounce R nor L

Fucking fantastic explanations my dude, I'm super glad I found your video :)

Why not just use pass by const reference instead of the move semantics?

I have one question, is this useful when you have static arrays?

You should really run your code time to time to show that it is working. In my code, both foo methods called copy constructor.

I love your tutorials. They are clear and excellent paced.

Great Video! I understand a lots with you. Thanks so much! (Not important but just mention that I agree with Taras)

Excellent explanation:
1) Explains what lvalue and rvalue are
2) Explains what lvalue reference and rvalue reference are.
3) Explains how they enable function overloading => they will also result in constructor overloading
4) Introduces Move constructor (that will be called implicitly now instead of Copy constructor when dealing with rvalues)
5)

How would you implement those functions?

I have always just used const references

but I might be able to find a use for this, I just don't see any reason to force it's use in my code

How to goal kick lmao

finally the video i was looking for !!!! u r my hero

where can I download the ppt?

Good explanations on the move semantics ! Thank you !

Bo, I'm not sure if it was mentioned in the history of comments, but should you ever redo this (very nice) video, you might want to discuss copy elision. Some viewers may be at a loss to explain why their move constructor does not get called because the compiler is allowed to elude copying (darn smart compilers). Nice work though... Love your videos!

You, sir, have some of the clearest explanations of the complicated C++11+ examples I've seen - and I've read a lot of them. Thank you for taking your time to make these, I will recommend your channel to others learning C++.