It's a shame how bad this presentation is prepared. Hopefully nobody starts learning concurrency from here. Don't get me wrong, I like most of the Fedor talks, but in this one, I'm not sure what's the point of showing some performance results without providing explanation.

I wonder how the results would have been in a bare-metal embedded system, like cortex-m or avr core

It's pretty amazing that myself as a very mid rust dev knows this is UB in 2024, where it takes a genius c++ dev to figure this out in 2016. Society has come a long way.

I'm now very happy with std::string::containts() 🙂

quite a few processors have popcount procedure

Nice speaker, but everybody using Visual Studio 2022. Why bother GDB? This is too simple, a waste of time.

27:05 Also: You can't have space in paths or file name. You can't even escape it. So, if you need to (which can happen if your install directory for example has a space and you have an install target in make) it can break.

"My data or yours?: Orchestrating the movement and placement of data on large multicore systems" kzfaq.info/get/bejne/b7-WobdktM6zXZs.html

Finally an understandable and comprehensive explanation! Thank you for this presentation.

That gentleman looks so much like the cousin of Bjourne, cool presentation

I gave up after 15 minutes, it felt there was almost no actual content. I'm not sure I'm convinced I want the book.

47:51 Thank you for finally explaining Rust lifetimes to me!

Essentially, any struct/class can be a "Shape" as long as it implements the interfaces that Shape requires, and that is amazing, that's what interfaces should just be, without inheritance. This is effectively Go's Interface

Good lecture! Did you use some specific tool for the graphs?

I don't get why people hate loops so much.

At 9:23, why can't you use "this" as a pointer of the base event type in the 'dispatch' function so you don't have to overload in the state class?

four videos later I finally (kinda) get what coroutines are...

Gratest knowledge shared! Many thanks. I am wonder that; can we also say that temporaries are inherently rvalues in C++?

THIS GUY! ... every talk he did i watched so far is worth its time in gold

at this point whenever I see herb's talks I just assume it's a bunch of talk and no action - nothing will actually come out of it. And then I just don't bother because it will just lead to disappointment.

if a unique pointer is the same in memory as a raw pointer, does that mean that I can reinterpretcast a raw pointer as a unique pointer and have it call the destructor?

Which will be the first compiler to support this? Also, avoid using those underscores.

Dynamic polymorphism personified!🎉

Sutter is determined to destroy C++. 😂😂😂

How does this compare to C++20 chrono?

0:19 actual talk starts here

I tried the expt-relaxed-constexpr flag because I wanted to do something very simple: just read constexpr global constants like those in std::numeric_limits. It caused all sorts of weird bugs. Nvidia needs to actually put in the work to fix this, make it usable, and remove the 'experimental' part.

1:16:17 no gamedev lol, probably runs nothing but java apps in production

Great talk. But I was not able to understand the disadvantage that you discussed of PIMPL and handle, that is 2 definition for one declaration. Can someone explain that to me or point me to some article where I could read about this.

C++ always choose the worst readable design. Pipes looks right, like in any other languages

I'm just happy I've never asked mom to buy an animal

can I start c++20 without knowing c++???

so where to find these algorithms origin?

Can someone explain the difference between void_t and enable_if and when to use each?

I stop use smart pointer, instead we make pointer as in C. We have another code manage to collect all this and making analyze where we must freeing resource.

Great talk!

So where's the drum? :)

C++ needs to be called C++++++++ nowadays

This talk was LAME the guy spent firts 15 minutes playing trivia ... I mean this was more of a Come lets play trivia than a talk ...

Reminds me of Fortran.

Yes and c++ itself sucks now

C++ libraries like std::chrono are the biggest argument for C++ against C. All the safeties and convenience without any loss of performance.

I think every developer instinctively has felt that the "virtual functions are slow" claim is overly generalized. Virtual functions have a practical purpose, and that practical purpose can outweigh a need for performance. And given a proper context, the correct implementation of virtual functions will also yield performance gains. What is surprising here is that compiler optimization and cpu management seems to be a decade or two ahead of what developers are thinking.

crowd is dead but good talk no mention of using rundll32 to just run the dll though?

This is big...

at 4:06, std::array is in cpu memory. How GPU can access it in kernel function? It not use cudaMemorycpy copy memory from host to device.

I used to really love Herb's talks until I realized the talk was usually the only thing to come out of them :( maybe a prototype on godbolt.

this is by far my favoirite C++ talk!!

Your talks are very clear. Thanks for educating a new generation of CPP users.