https://dev.to/wallyqs/gos-map-iteration-order-is-not-that-r...
(Which I find a hilarious second order example of Hyrum's law - if you add true randomness to prevent people from depending on the iteration order, they might use it as a way to randomly access items in the map!)
At that point their debug builds would do a "coin toss" with 50.3% chance to be heads during hash table insertion and he expected some idiots would use that to generate random bits then be annoyed if it breaks. I believe in production it's entirely seeded from ASLR, so you're actually leaking address layout info if you try to use these bits as entropy instead of just to make the hash table defeat your bad unit tests.
At the time I thought this was a questionable decision that'd cause nightmare debugging scenarios, where someone writes code accidentally depending on insertion-ordered iteration, only to deploy it on a python runtime without it (<=3.5). I'm sure this has happened to someone, but at least it hasn't happened to me.
Reference: https://stackoverflow.com/a/60775590
Hyrum and his dedicated self-proclaiming website reminded me of the gracelessness in the 3rd example of r/iamverysmart: Self-quoting
And lets be real. There is no contract, and any one that is made will inevitably be broken.
Or other measure of their importance.
Does the C library change break a major distro? Or just some obscure program with three users?
The key lesson to take away is: if you want something to be an implementation detail, make sure to have multiple differing implementations :)
Why bother? We're not even able to guard against well establish contracts from changing and breaking compatibility.
When people don't know which implementation will be used, they tend to stick to the standard or the documentation.
We see this in places like the C language or in Common Lisp. Library writers must take into account that the implementation they use their library on may not be the same as the implementation their users will use.
What are other approaches?