Re: [Sbcl-devel] Warning from CALL-NEXT-METHOD expansion in SB-PCL

[mrd <md...@an...>]

I've composed a test-case for this scenario.  It turns out, as you may
have suspected during our conversation on IRC, to be related to the
debug level of 3.


CL-USER> (lisp-implementation-version)
"0.9.16.6"
CL-USER> (proclaim '(optimize (debug 3)))
; No value
CL-USER> (defclass test ()
           ())
#<STANDARD-CLASS TEST>
CL-USER> (defmethod test-method ((c test))
           (call-next-method))
; in: LAMBDA NIL
;     (SB-PCL::FAST-LEXICAL-METHOD-FUNCTIONS
;    ((C) SB-PCL::.NEXT-METHOD-CALL. (C) NIL :CALL-NEXT-METHOD-P T
;     :NEXT-METHOD-P-P NIL :SETQ-P NIL :METHOD-NAME-DECLARATION
;     ((TEST-METHOD (TEST))) ...)
;    (DECLARE (SB-PCL::%CLASS C TEST)) (BLOCK TEST-METHOD (CALL-NEXT-METHOD)))
; --> SB-PCL::BIND-FAST-LEXICAL-METHOD-FUNCTIONS FLET CATCH BLOCK 
; --> SB-C::%WITHIN-CLEANUP BLOCK SB-PCL::FAST-CALL-NEXT-METHOD-BODY IF IF 
; --> SB-PCL::INVOKE-EFFECTIVE-METHOD-FUNCTION LET COND IF COND IF PROGN 
; --> LET* WHEN COND IF PROGN SB-PCL::CLOS-SLOTS-REF BLOCK SVREF 
; ==>
;   (AREF (THE SIMPLE-VECTOR SB-PCL::SLOTS) SB-INT:INDEX)
; 
; caught WARNING:
;   Asserted type (MOD 536870911) conflicts with derived type
;   (VALUES (OR FUNCTION SB-PCL::METHOD-CALL SB-PCL::FAST-METHOD-CALL) &OPTIONAL).
;   See also:
;     The SBCL Manual, Node "Handling of Types"
; 
; compilation unit finished
;   caught 1 WARNING condition
STYLE-WARNING: implicitly creating new generic function TEST-METHOD
#<STANDARD-METHOD TEST-METHOD (TEST) {AFD8E59}>
CL-USER> 

-- 
;; Matthew Danish -- user: mrd domain: cmu.edu
;; OpenPGP public key: C24B6010 on keyring.debian.org