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

Use string->uninterned-symbol instead of gensym

Browse Source 
The reason these functions used gensym to begin with
was that fresh variables resulted in confusing error
messages of the form "Expected a, but got a".

An upcoming commit fixes these error messages, so
the gensym is replaced.

original commit: b214fa01c11c6fc74f24318bc702bbb5ad915822
This commit is contained in:
Asumu Takikawa 2013-10-16 14:36:06 -04:00
parent ef1bb66deb
commit ccdaf6e564
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pkgs/typed-racket-pkgs/typed-racket-lib/typed-racket/rep/type-rep.rkt
View File

@ -750,6 +750,11 @@
(list syms (Poly-body* syms t))))
(list nps bp)))])))
;; Helper for fresh match expanders below, creates a
;; fresh name that prints the same as the original
(define (fresh-name sym)
(string->uninterned-symbol (symbol->string sym)))
;; This match expander creates new fresh names for exploring the body
;; of the polymorphic type. When lexical scoping of type variables is a concern, you
;; should use this form.
@ -761,7 +766,7 @@
(app (lambda (t)
(let* ([n (Poly-n t)]
[syms (hash-ref name-table t (lambda _ (build-list n (lambda _ (gensym)))))]
[fresh-syms (map gensym syms)])
[fresh-syms (map fresh-name syms)])
(list syms fresh-syms (Poly-body* fresh-syms t))))
(list nps freshp bp)))])))