failed AVER: (EQL (SB-C::BLOCK-COMPONENT BLOCK) SB-C:COMPONENT)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Failed AVER in code with invalid function calls. This is lower priority because it's invalid, but the invalid calls should (in SBCL practice) produce warnings rather than this result.
(defun f42 ()
(declare (optimize (safety 3)))
(flet ((%f (&optional x) 2))
(%f)
;; Two of the %f calls are erroneous, with an extra argument
(flet ((%f6 (&key (k (%f (%f -1 (%f -2 -3))))) 0))
5)))
===>
failed AVER:
(EQL (SB-C::
[...]
Backtrace:
0: (SB-INT:BUG "~@<failed AVER: ~2I~_~S~:>" (EQL (SB-C::
1: (SB-IMPL:
2: (SB-C::
[...]
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
Lisp is allowed to signal an error at compile time, however in this case (too many arguments) the error is specified to be of type PROGRAM-ERROR, and SB-INT:BUG is not a subclass of PROGRAM-ERROR.