Better error message for expand.
Bug #163219 reported by
Michael D. Adams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ikarus Scheme |
Fix Released
|
Low
|
Abdulaziz Ghuloum |
Bug Description
The error message when running expand on a non-expression is difficult for a new user to understand. It should explain that expand doesn't work on defines unless they are wrapped in "(let () ...)".
> (expand '(define-
Unhandled exception
Condition components:
1. &error
2. &who: expander
3. &message: "invalid expression"
4. &irritants: ((define #{g0 |58AR2IT9On3HXN9X|} (make-record-
Changed in ikarus: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Would new users be using expand? Notice that the error comes from the expander, which is the same error you'd get when you type
(+ (define-record-type foo) 14)
Would saying "definition found where an expression was expected" be any better?