[OT] Move semantics in a nutshell

[monkyyy]

On Monday, 10 November 2025 at 12:42:10 UTC, Timon Gehr wrote:
> In your example you also had to think about "hmmm what are the 
> possible `T[]`. Actually you had to think about "hmmm what are 
> the possible combinations of `int`s and `T[]`s.

That ubyte code was a static array

A static 256 length array with a ubyte index has no "specific 
limitations on its bit pattern" if it fails its a os level 
failure and I couldn't operate anyway.

> Look no further than encryption-based ransomware (e.g. 
> EternalBlue exploited by WannaCry and NotPetya/ExPetr). It's 
> not a theoretical scenario at all,

> I don't think D is the most fruitful ground for these 
> "fail-safe" experiments

Such encryption is **very** well defined, as is what version of 
rm -* will delete your harddrive.

They escape the box using *well-defined undefined-behavior*, keep 
in big databases with lots of formal writting, with lots of 
theory and powerpoints and terminology; that walter for his 
faults as an airplane surgeon, thought "we can fix this quickly 
with an api solution" while ranting and raving that the c 
committy were full of idiots.

Walter is over confident calling it the most important thing 
ever, and the range api was an ovisous next step, then merging 
data structures into the std but... opps. Oh well. We have 3 
template languages, and 3 suggestions for memory safety, c++, 
rant in long spec call users bad if they violate your rules, rust 
and its piles of math, walter and "guys lets just make a breaking 
change around string handling" and shipping a data structure.

Im for api level solutions and calling slow moving "experts" 
idiots