coops: redefining things breaks methods

[megane]

Tested with Version 4.7.5 (rev 5fe91ae)

;;; This works as supposed:

(require-extension coops)
(define-class <a>)
 (define-method (foo (i <a>))
   (print "foo v1"))

(define obj (make <a>))
(foo obj)

(define-class <a>)
 (define-method (foo (i <a>))
   (print "foo v2"))

(foo obj)

;; Output:
;; foo v1
;; foo v1 <- this is OK

;; Now, same with modules:

(module a
 *
 (import chicken scheme)
 (use coops)
 (define-class <a>)
 (define-method (foo (i <a>))
   (print "foo v1"))
 )

(import a)

(define obj (make <a>))
(foo obj)

(module a
 *
 (import chicken scheme)
 (use coops)
 (define-class <a>)
 (define-method (foo (i <a>))
   (print "foo v2"))
 )

(import a) ;; <- commenting this doesn't matter
;; Also, using different name altogether for the second module doesn't matter

(foo obj)

;; Output:
;; foo v1
;; Error: (foo) no method defined for given argument classes: (#<coops standard-class `<a>'>)

[sjamaan]

We discussed this on IRC, and I think we came to the conclusion that this is expected (if somewhat unfortunate) behavior. The classes might have the same name and be from the same module, but the class objects are entirely unrelated and don't know about eachother's existence.

If you rename the second module to b, and don't import it, it works. If you rename but DO import, the class is redefined and the obj is of the old class. The new foo procedure you defined in the second module overwrites the foo procedure defined in the first module instead of extending the earlier generic procedure. If module a is imported in b, it will extend properly.

If y'all agree this is not a bug, please close the ticket.