these are relevant if you, for some reason, want to write your own ELF parser, to load Linux executables without using the system loader.
it comes up fairly often when analyzing (or creating) advanced malware for linux
The real value of std::move is cases where you to HAVE to (effectively) make a deep copy, but still want to avoid the inefficiency. std::move supports this because moving means "stealing" the value from one variable and giving it to another. A common use case is move constructors for objects where you need to initialize the object's member variables, and can just move values passed by the caller rather than copying them.
Another important use case for std::move is returning values from functions, where the compiler will automatically use move rather than copy if available, allowing you to define functions returning large/complex return types without having to worry about the efficiency.
It’s ok for small things but even once you get into the command buffer range it’s slow slow slow without dma.
I've read various accounts of people trying to reclaim lost baggage and it's a Kafkaesque process designed to be totally useless
But the railway operators are 50% nationalised now. Northern, TransPennine, South West Railway, LNER, Greater Anglia, c2c, ScotRail, Southeastern, TfW are all government owned.
And the forerunner in increasing fares the last couple of years has been...the government. They renationalised various operators during and after COVID and are now busy decreasing rail subsidies and increasing fares.
(yes even with the freezing of some fares in April. It's only some fares. And prices had been going up multiple times a year in many places for a few years. There is a wider picture and other schemes happening pushing up prices)
Maybe Great British Rail will slowly and surely return us to a less mean system. Time will tell