The C++ rvalue lifetime disaster
Arno Schoedl - a year ago
Rvalue references have been with us since C++11. They have originally been introduced to make moving objects more efficient: the object an rvalue reference references is assumed to go out of scope soon and thus may have its resources scavenged without harm. The C++ standard library, for example std::cref or std::ranges, makes use of yet another aspect of rvalue references: since they go out of scope soon, it is assumed unsafe to hold on to them beyond the scope of the current function, while lvalue references are considered safe. We, too, found this assumption to be very useful for smart memory management, in particular in generic code...
Jobs with related skills
Software Engineer für Apple CarPlay (m/w/d)
e.solutions GmbH
·
1 month ago
Ingolstadt, Germany
Hybrid
Software System Engineer / Software Architect (m/w/d)
KRÜSS GmbH
·
14 days ago
Hamburg, Germany
Hybrid
SPS-Programmierer / Systemtechniker (m/w/d)
Trolli GmbH
·
1 month ago
Fürth, Germany
+1
Hybrid
Field Application Engineer (FAE) (m/w/d)
Lauterbach GmbH
·
1 month ago
Höhenkirchen-Siegertsbrunn, Germany
Related Videos