xxxxxx@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:

> I'll see that I add optional arguments to the R6RS hash functions to
> take a salt and bound.

Actually, it seems the typical salting strategy is to take a hash
function that has the salt built in, presumably seeded at program
start-up.  This will work just fine with R6RS and draft 6 of SRFI-126.
Passing the salt to each call to the hash function seems excessive?

One could also specify e.g. (make-string-hash salt) to generate a
string-hash with a given salt.  That way it can be ensured that a hash
table behaves deterministic/same across runs of the program, which might
be valuable for testing, benchmarks, etc.

Taylan