Explore >> Select a destination
|
You are here 
|
pagefault.blog | ||
| | | | |
blog.knatten.org
|
|
| | | | | In which I briefly mention what pure functional programming is, explain why this can be slow in C++, and use move semantics to solve that problem. Be warned that this post is a bit longer than usual for this blog, and that it assumes more knowledge of C++11 than my posts usually do. Pure functional... | |
| | | | |
mytechblog.blogtown.co.nz
|
|
| | | | | Lvalues, rvalues, glvalues, prvalues, xvalues, help (2018) :) Back before C++11, there were two value categories, lvalue and rvalue. The basic intuition was tha | |
| | | | |
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. | |
| | | | |
blog.skylight.io
|
|
| | | One of the coolest features of Rust is how it automatically manages resources for you, while still guaranteeing both safety (no segfaults) and high performance. Because Rust is a different kind of programming language, it might be difficult to understand what I mean, so let me be perfectly clear: * In | ||
