|
You are here |
hellocplusplus.com | ||
| | | | |
herbsutter.com
|
|
| | | | | C++ "move" semantics are simple, and unchanged since C++11. But they are still widely misunderstood, sometimes because of unclear teaching and sometimes because of a desire to view move as something else instead of what it is. This post is an attempt to shed light on that situation. Thank you to the following for their... | |
| | | | |
www.kuniga.me
|
|
| | | | | NP-Incompleteness: | |
| | | | |
pagefault.blog
|
|
| | | | | C++11 move semantics can be a source of misunderstandings if the mechanics are not understood. This post clears up the most common one. | |
| | | | |
mklimenko.github.io
|
|
| | | Every time I work with a C library, I miss the power and capability of the type system C++ provides. That's why I developed a simple C++17 header-only helper library to pack the multiple type-dependent C-style functions into single overload deduced at compile-time. No external libraries are required. Repo link: https://github.com/MKlimenko/plusifier. Currently, it's just the header and a compile-time test file, CMake integration coming soon. | ||