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

> - I will specify that the hash function passed to make-hashtable *may*
>   be passed a second bound argument, and the hash functions will take
>   optional bound arguments.
>
> This covers the gigantic tables use-case.
>
> I'm not entirely happy about the last one, but can't think of a better
> solution.  The other two I'm fairly happy about, because they're very
> non-intrusive changes and cleanly solve our problems.

I decided to slightly break R6RS compatibility there, since it's for
very rare cases anyway: as long as the built-in foo-hash are extended
alongside make-hashtable, code like (make-hashtable string-hash ...)
keeps working as is; the only thing affected are custom hash functions,
which are probably a pretty rare use-case, and they only need to accept
one more argument and may just ignore it.

That avoids the weird "may pass a second argument" semantics.

Taylan