(cookieplmonster.github.io)

1371 points yett | 5 comments | 23 Apr 25 14:00 UTC | HN request time: 0.847s | source

Show context

amenghra ◴[23 Apr 25 18:08 UTC] No.43774928[source]▶

IMHO, if something isn’t part of the contract, it should be randomized. Eg if iteration order of maps isn’t guaranteed in your language, then your language should go out of its way to randomize it. Otherwise, you end up with brittle code: code that works fine until it doesn’t.

replies(11): >>43774993 #>>43775199 #>>43775210 #>>43775344 #>>43775361 #>>43775510 #>>43775759 #>>43776084 #>>43776311 #>>43776598 #>>43778608 #

tantalor ◴[23 Apr 25 21:03 UTC] No.43776598[source]▶

>>43774928 #

Nope. You have to remember https://www.hyrumslaw.com/

  With a sufficient number of users of an API,
  it does not matter what you promise in the contract:
  all observable behaviors of your system
  will be depended on by somebody.

If you promise randomization, then somebody will depend on that :)

And then you can never remove it!

replies(2): >>43778253 #>>43780617 #

1. timewizard ◴[24 Apr 25 00:43 UTC] No.43778253[source]▶

>>43776598 #

> If you promise randomization

You don't. You say the order is undefined.

replies(2): >>43778894 #>>43778928 #

2. dwattttt ◴[24 Apr 25 03:00 UTC] No.43778894[source]▶

>>43778253 (TP) #

You can randomly not randomise it :)

3. __float ◴[24 Apr 25 03:07 UTC] No.43778928[source]▶