c weekly - ep 260 - c 's most vexing parse: how to spot it, why it exists, and how to avoid it
Published 3 years ago • 11K plays • Length 5:35Download video MP4
Download video MP3
Similar videos
-
9:05
c weekly - ep 263 - virtual inheritance: probably not what you think it is
-
4:13
c weekly - ep 261 - c 20's new consteval keyword
-
9:56
c weekly - ep 259 - crtp: what it is, some history and some uses
-
7:35
c weekly - ep 264 - covariant return types and covariant smart pointers
-
11:32
c weekly - ep 271 - string.clear() vs string = ""
-
6:31
c weekly - ep 112 - gcc's leaky abstractions
-
12:46
c weekly - ep 231 - multiple destructors in c 20?! how and why
-
5:26
c weekly - ep 160 - argument dependent lookup (adl)
-
5:42
c weekly - ep 267 - c 20's starts_with and ends_with
-
8:52
c weekly - ep 276 - c 20's conditionally `explicit` conversions
-
5:14
c weekly - ep 168 - discovering warnings you should be using
-
10:28
c weekly - ep 346 - c 23's bind_back
-
16:53
c weekly - ep 269 - how to use c 20's constexpr std::vector and std::string
-
8:17
c weekly - ep 262 - std::string's 11 confusing constructors
-
6:48
c weekly - ep 241 - using `explicit` to find expensive accidental copies
-
15:16
c weekly - ep 343 - digging into type erasure
-
19:56
c weekly - ep 274 - why is my pair 310x faster than `std::pair`?
-
9:47
c weekly - ep 277 - quick perf tip: avoid integer conversions
-
8:38
c weekly - ep 265 - c 20's std::bit_cast