wanted: better error reporting in ASSERT
Bug #789497 reported by
Tobias C. Rittweiler
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Low
|
Unassigned |
Bug Description
I wish (ASSERT (FOO X Y)) reported "Assertion (FOO <val1> <val2>) failed."
Changed in sbcl: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: easy feature |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The patch implements the proposed behavior for ASSERT. Tests are included.
I originally used (CONSTANTP PLACE ENV) but i had to take ENV out because otherwise the build failed. Presumably it happened due to early use of ASSERT.
During tests of the patch, i encountered an error in float.pure.lisp in the expression (assert (typep (nth-value 1 (ignore-errors (float-radix "notfloat"))) 'type-error)): the subexpression (nth-value ...) seems to return NIL. My macro expansion is here: http:// paste.lisp. org/display/ 136940 . Am I doing something wrong? or is it a bug in IGNORE-ERRORS?