" Moves one piece of candy in column col, if necessary and possible, so that the box
* element in row 0 of column col contains a piece of candy, as described in part (a).
* Returns false if there is no piece of candy in column col"
This instruction makes no sense, if we are moving something inside the column it would never return false.
Sorry to be rude, but by experience i see some company who lack of architectural strategy blaming their framework or worst, their programming language when times are hard.
For sure an issue with experimental Rust features is expectable, however if there is testing or deployment issue the lack of modularity is to blame first.
I started using arch on a VM 10 years ago and now it runs my raspberry and any laptop i buy as the single OS.
Even if it has changed the init system during past years, system administration always looked easy enought to be performed with their helpfull wiki.
Most users would prefer turnkey solutions like Manjaro instead, but when you know exactly which software you need to run your system ArchLinux become a perfect solution.