Комментарии:
good one, got the basics thanks
Ответить"some" views not supporting iteration while const is a very nasty behaviour. More so since it is non-deterministic (at least at glance). Couldn't it be solved with mutable keyword? Recommending using auto&& so stuff works doesn't seem like the best idea as it is the first step to sacrifice const correctness.. :(
Otherwise - great talk! The more I delve into the move semantics the more they seem unfinished. The "valid but unspecified state" effectively means that unless your compiler supports use-after-move detection then you shouldn't ever move a named variable or else you risk shooting yourself in the foot. If that detection was default, then the compiler would move a lot of stuff automatically. This way, you're forced to optimize by hand a risk a bug.
Thank you for this talk.
ОтветитьBrilliantly explained. Thank you Mr Josuttis.
Ответитьbest explanation on move semantics
ОтветитьThis is a perfect explanation what the move semantics is.
Ответитьthe best move semantics out there.
ОтветитьThank you so much for deeply understanding of the move semantic and universal forwarding.
ОтветитьGreat Talk!!!!!
Ответитьgreat talk as always
ОтветитьExcellent talk
ОтветитьThank you so much for these amazing videos. I've borrowed Nicolai's book "The c++ Standard Library", You are so inspirational and give great examples, thank you Nicolai.
Ответитьhow to get slide?
Ответитьjust amazing
ОтветитьExcellent, clear talk and the best on the subject. thank you!
ОтветитьGreat example! Thanks to this video, now I have better understanding on move semantics.
ОтветитьThe best talk ever on this topic.
ОтветитьThank you for making these videos, Mr Josuttis.
ОтветитьDear @CppCon, I would love to get the slide deck of this talk. Is sharing it a possibility?
ОтветитьThank you for explaining why std::forward exists, it makes it easy to understand what it does and when you have to use it.
Ответитьvery nicely explained, thanks.
ОтветитьWell explained! Thx a lot!
ОтветитьThank you for the nice talk! "Back to Basics" to the bone.
Why do destructors in derived classes destroy move semantics?
I wore the spine out of his 1st edition of "The C++ Standard Library". Thanks so much for that book, it very much helped me learn how to use the C++ standard library!
Ответить🖖
ОтветитьReally informative
ОтветитьQuite a complete summary that exposes most if not all the move semantic intricacies.
ОтветитьThe last part about universal reference was very useful.
ОтветитьThank you for the talk! I am learning C++ as a novice and really enjoying these sessions!
Very clear, with specific examples to explain the context and the value of the concept. 5/5!
Thank you Nicolai for such informative and detailed explanation of move semantics.
It would be interesting to read your ne books as well. ;)
Question:
It's not so nice having this T&& or auto&& for a universal reference since the type is vague.
Would it be possible to confine the type with concepts / requires T is MyClass somehow?
Also is there any plan to 'fix' forwarding in C++23?
Very clear, concise and meticulous talk, much appreciated.
ОтветитьBrilliant explanation.
ОтветитьA thoroughly excellent talk, this is by far the clearest and least confused explanation of C++ move semantics I have encountered. Bravo!
Ответить