[m-users.] Suggestion: hash_table should use a hash function instead of a hash predicate

Julien Fischer jfischer at opturion.com
Wed Sep 30 14:12:24 AEST 2020


On Wed, 30 Sep 2020, Mark Brown wrote:
> Does using a combined higher-order type and inst help here, instead of
> switching to a function? Then the inst for hash tables would just be
> unique (or ground, with the current workaround for the lack of nested
> uniqueness), and code that sensibly uses the current interface should
> keep working.
> Speaking of the lack of nested uniqueness, maybe version_hash_table is
> a better choice for a recursive data structure? It does not require
> uniqueness.

For reference: there was some of discussion around hash tables on the
reviews list in Feburary, see: <http://lists.mercurylang.org/archives/reviews/2020-February/021113.html>.


More information about the users mailing list