Errors should reflect where they occurred (wishlist)

Bug #1739254 reported by Paul F. Dietz on 2017-12-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I would find it useful if error objects had additional information in them that reflects where the error occurred.

My use case for this is determining when two different errors are "different", so distinct test cases can be generated for each of them, and also so high frequency unfixed errors can be silenced during random test generation.

Another use case would be for a user to identify the line in a source file where the error happened.

Explicit calls to ERROR (or allocation of error condition objects) in source code can access information about the source file and possibly line number, and this could be stored in the error object in additional slots.

Errors signaled down in library code (for example, #'car checking if the arg is a LIST or not) would not want to signal that the error occurred there, but rather somewhere back up the stack in user code. This suggests it might be useful to make stack traces be first class objects visible to the user, or at least to the error object creation code.

Stas Boukarev (stassats) wrote :

That information is already available and slime takes advantage of it.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers