debugger invoked on a SB-INT:BUG in thread 27726:
fasl stack not empty when it should be
-333: "CHECK-TYPE TYPE-ERROR-DATUM place"
- (reported by Tony Martinez sbcl-devel 2004-05-23)
- When CHECK-TYPE signals a TYPE-ERROR, the TYPE-ERROR-DATUM holds the
- lisp symbolic place in question rather than the place's value. This
- seems wrong.
-
334: "COMPUTE-SLOTS used to add slots to classes"
(reported by Bruno Haible sbcl-devel 2004-06-01)
a. Adding a local slot does not work:
(test-um12 17))
fails with NO-APPLICABLE-METHOD.
-338: "MOP specializers as type specifiers"
- (reported by Bruno Haible sbcl-devel 2004-06-11)
-
- ANSI 7.6.2 says:
- Because every valid parameter specializer is also a valid type
- specifier, the function typep can be used during method selection
- to determine whether an argument satisfies a parameter
- specializer.
-
- however, SBCL's EQL specializers are not type specifiers:
- (defmethod foo ((x (eql 4.0))) 3.0)
- (typep 1 (first (sb-pcl:method-specializers *)))
- gives an error.
-
339: "DEFINE-METHOD-COMBINATION bugs"
(reported by Bruno Haible via the clisp test suite)
should signal an invalid-method-error, as the :IGNORE (NUMBER)
method is applicable, and yet matches neither of the method group
qualifier patterns.
+
+340: SETF of VALUES using too many values
+ (reported by Kalle Olavi Niemetalo via the Debian bug system, with
+ bug id #256764)
+
+ (let ((a t) (b t) (c t) (d t))
+ (setf (values (values a b) (values c d)) (values 1 2 3 4))
+ (list a b c d))
+ should return (1 NIL 2 NIL), but under sbcl-0.8.12.x returns
+ (1 2 3 4) instead.