[armedbear] #485: Non-congruent generic method signatures cannot be eval'd

[armedbear]

#485: Non-congruent generic method signatures cannot be eval'd
-------------------------------+-----------------------
      Reporter:  Mark Evenson  |      Owner:  (none)
          Type:  defect        |     Status:  new
      Priority:  major         |  Milestone:  1.8.1
     Component:  interpreter   |    Version:  1.8.1-dev
    Resolution:                |   Keywords:
Parent Tickets:                |
-------------------------------+-----------------------

Comment (by Mark Evenson):

 jackdaniel schooled easye on #abcl:

 {{{
 l easye: the congruency between the gf and the method is defined (among
 other rules), that method must have all key arguments from the generic
 function
 18:04:06
 jackdaniel it may have more though
 18:04:45
 jackdaniel when you implicitly define the generic function via defmethod,
 and defmethod has &key arguments, the generic function is defined as
 (defgeneric foo (a &key)) [i.e for (defmethod foo ((a integer) &key z d))
 18:05:02
 jackdaniel so they are in fact congruent
 18:09:45
 easye Alright.  That's right:  one doesn't typically use keyword arguments
 with generic functions for this reason.
 }}}

-- 
Ticket URL: <https://abcl.org/trac/ticket/485#comment:1>
armedbear <https://abcl.org>
armedbear