> I'm with Antoine here - being able to force a particular seed still > matters for testing purposes. However, the documentation of the option > may need to be updated for 3.3 to emphasise that it should only be > used to reproduce sporadic failures. Using it to work around > applications that can't cope with randomised hashes would be rather > ill-advised. In the tracker, someone proposed that the option is necessary to synchronize the seed across processes in a cluster. I'm sure people will use it for that if they can. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4