/explore
|
You are here 
|
blog.knatten.org | ||
| | | | |
ericniebler.com
At GoingNative back in September, Andrei Alexandrescu posed an interesting question about API design and C++11 that has had me scratching my head for a month. It was about the design of std::getlin... |
|
| | | | | ||
| | | | |
www.foonathan.net
When C++11 introduced move semantics, it also added two important helper functions: std::move and std::forward. They are essential when you want to manually indicate that you no longer care about an object or need to propagate the value category in generic code. As such, Ive used them countless times in the past. However, they are functions. Plain, old, standard library functions. This is problematic for multiple reasons. |
|
| | | | | ||
| | | | |
hellocplusplus.com
Learn the basics of C++ move semantics and how to use this language feature. This article is useful for programmers of all skill levels. |
|
| | | | | ||
| | | | |
mcyoung.xyz
[AI summary] The text provides an in-depth exploration of SIMD (Single Instruction, Multiple Data) programming, focusing on its application in optimizing algorithms like base64 decoding. It outlines the challenges of writing portable SIMD code across different architectures, the role of compilers and instruction sets, and the importance of avoiding branches in performance-critical code. The article transitions into a practical example of implementing a SIMD version of the base64 decoding algorithm, emphasizing the use of shuffles and data reordering to efficiently process data in parallel. It also touches on the trade-offs between using intrinsics, portable SIMD libraries, and compiler optimizations, while highlighting the complexities of cross-platform deve... |
|
| | | |||
