bug#37461: define-generic doesn't promote equal? to generic

2019-09-19 Thread Rob Browning
Rob Browning writes: > You can work around the problem by stashing equal? somewhere else, and > then define-generic will work after a (define equal? #f). Presumably > you'd then need to define a base specialization using the original > equal? or do something equivalent. It looks like while

bug#37461: define-generic doesn't promote equal? to generic

2019-09-19 Thread Rob Browning
Version: 2.2.6 scheme@(guile-user)> (use-modules (oop goops)) scheme@(guile-user)> equal? $1 = # scheme@(guile-user)> (define-generic equal?) scheme@(guile-user)> equal? $2 = # The same appears to be true for other primitives like + too, but if I'm reading it right, this makes it