[m-rev.] for review: ulength/ucount

[Zoltan Somogyi]

For review by anyone. The main things I am seeking feedback on are
these:

- For the set modules, some define count as both a func and as a pred, while
  some others define it only as a func. Should we add pred versions as well?
  This could cause compatibility issues, due to issues with "which version
  did I just curry". But then, the gratiutous differences between
  otherwise-compatible modules can also be annoying.

- I added to set.m a list of all the modules that implement sets. I can add
  something similar to map.m and to list.m, but I am on the fence about
  whether we should instead add a central file listing all the groups of
  related modules. This would allow better treatment of e.g. arrays
  (which are sort-of maps whose keys are integers, just as sparse_bitsets
  are sets whose values are integers) and their versioned cousins.

Opinions?

BTW, before commit, I intend to fix the out-of-order entries of the
one_or_more/one_or_more_map modules in NEWS.md.

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.ucount
Type: application/octet-stream
Size: 1145 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20260102/5145cd82/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.ucount
Type: application/octet-stream
Size: 42784 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20260102/5145cd82/attachment-0003.obj>