Re: map-char-table, optimize-char-table and `equal' comparisons

[Kenichi Handa]

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

> Both map-char-table and optimize-char-table compare consecutive values
> using `equal' to determine whether to merge them into ranges.

> I can see that it may sometimes be useful, but it is dangerous since it
> may lose object identity information (obviously) and more importantly
> because `equal' can fail when comparing cyclic objects.

> I happened to be manipulating char-tables that map chars to other
> char-tables, sometimes in cyclic ways and that makes it impossible to
> use map-char-table ;-(

> Any objection to changing the internal comparison predicate to `eq'?

I remember that I intentionally made the comparison
predicate `equal' so that optimize-char-table can reduce the
number of elements for some kind of char-table.

How about adding the new property/attribute :test to
char-table (like make-hash-table) and make the default to
`equal'?

---
Kenichi Handa
address@hidden