Please also see the last comment/question here, which hasn't been answered yet: https://groups.google.com/g/scheme-reports-wg2/c/NZA9CIMRl48/m/zJ06IprvAwAJ

For R7RS-large, we export some bindings under different names (as by announcement of John). So, just making sure to export SRFI 101's "equal?" as "rlist=?" in (scheme rlist) solves at least the problem of overlapping bindings in R7RS-large (and would be consistent).

Am Do., 27. Aug. 2020 um 01:15 Uhr schrieb Arthur A. Gleckler <xxxxxx@speechcode.com>:
On Mon, Jun 22, 2020 at 6:24 PM John Cowan <xxxxxx@ccil.org> wrote:
Unfortunately, srfi-101:equal? is not necessarily compatible with r7rs:equal?.  The latter is free to recurse through records, as Chibi's implementation does, whereas the former insists that two records return #f unless they are eqv?.  A PFI should be added to warn implementers of this, and to caution users not to expect whatever the native semantics if they use srfi-101:equal?.  So the Right Thing is to indeed to reimplement srfi-101:equal? from scratch.

I just hope there are no other oddball equal? predicates hiding elsewhere in the SRFIs.

When one of you has a chance, would you please compose a PFN for this issue for me to add to SRFI 101?

Thanks.