Jun 13
A sleeping pad is not just about comfort. It is part of your insulation system, and the wrong pad can make a good sleeping bag feel like it failed.
Do you check R-value before buying one?
#CampingGear #RValue #WildernessSkills
1
3
10
1,293
Jun 12
95% don't even understand what an rvalue is...and it might be moved...so let them believe it
747
Jun 12
std::move creates a "rvalue reference" which gives the recipiant permission (but not obligation) to "move" the source value.
In general a "move" in C is expected to leave the source in a "valid but otherwise unspecified" state.
2
12
Jun 12
What happes to the source is whatever the thing that's doing the move (i.e. the function that accepts an rvalue ref) decides what should happen to it.
But the source still exists afterwards, and its destructor eventually runs, so you can't leave it in some indeterminate state.
8
Jun 12
std::move does nothing but convering a lvalue ref to an rvalue ref.
Actual moves are not destructive, because the original object still exists.
1
5
128
Jun 12
Oh, rvalues and lvalues are certainly very distinct. Lvalue references are comparatively simple and very old. Basically const pointers with some syntactic sugar.
Rvalue references, on the other hand ... yeah.
2
4
254
گو نه آکادمیکه و نه اکسپرسیو
فقط سادست و پراگماتیک (چه کصی گفتم)
آرایه ها توی گو ریفرنس ان درصورت که شبیه rvalue میمونن
260
1
2
385
OK, but it won't compile. Post increment returns an rvalue. Post decrement requires an l value. Same with following .
The post increment on the name makes sense (or it did for the first few decades).
1
3
160
std::move doesn't move anything, it just casts to an rvalue reference.
9
2
88
18,938
May 19
Sure, C lets you craft pointer values to write to like a portable assembler. But how did that end up responsible for lvalue references, rvalue references, and universal references? C spec is ~700 pages. C is 2000 . The extra pages didn’t come from C, no?
1
2
205
