I have now added new category Hashable with intent that domains
declare Hashable if and only if 'hashUpdate!' is properly
implemented. So 'hash' and 'hashUpdate!' are removed from
SetCategory.
AFAICS Hashable rarely can be declered at category level.
Probably it should be declared only if we can give
resonably good default implementation. For example I
added 'hashUpdate!' to Finite and implemented it in
terms of 'lookup'. I have made few exception when category
has small number of domains. But main case seem to be that
we can only declare Hashable at domain level. This means
that to inherit implementation we need to declare Hashable
along inheritiace chain. Due to this there are probably
cases which previously had 'hashUpdate!' but lost it
in transition.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/20230506123916.xpbfzxa75rjziezh%40fricas.math.uni.wroc.pl.
