suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Try to handle type errors in non-original syntax a bit better.

Browse Source
This commit is contained in:
Stevie Strickland 2008-07-03 12:03:18 -04:00
parent c9e8f6d6f6
commit 1aaa6995a1
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
collects/typed-scheme/private/tc-utils.ss
View File

@ -82,7 +82,12 @@
;; produce a type error, using the current syntax
(define (tc-error msg . rest)
(raise-typecheck-error (apply format msg rest) (list (locate-stx (current-orig-stx)))))
(let ([stx (locate-stx (current-orig-stx))])
;; If this isn't original syntax, then we can get some pretty bogus error messages. Note
;; that this is from a macro expansion, so that introduced vars and such don't confuse the user.
(if (syntax-original? stx)
(raise-typecheck-error (apply format msg rest) (list stx))
(raise-typecheck-error (apply format (string-append "Error in macro expansion -- " msg) rest) (list stx)))))
;; produce a type error, given a particular syntax
(define (tc-error/stx stx msg . rest)