Am Do., 14. Juli 2022 um 17:54 Uhr schrieb John Cowan <xxxxxx@ccil.org>:
It's been pointed out to me the eq- and eqv-comparators aren't as useful as they might be because they mandate default comparators.  I would like to change this by inserting the following language from SRFI 125 into SRFI 128 as a post-finalization note:

Implementations are permitted to ignore user-specified hash functions in certain circumstances. Specifically, if the equality predicate, whether passed as part of a comparator or explicitly, is more fine-grained (in the sense of R7RS-small section 6.1) than equal?, the implementation is free — indeed, is encouraged — to ignore the user-specified hash function and use something implementation-dependent. 

Comments?

In these certain circumstances, it should be allowed for an implementation not support comparator-hash-function and comparator-hash.

What does it actually mean in the context of SRFI 128 to ignore the user-specified hash function?