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

expander: repair extraction when using an existing Racket build

Browse Source 
Recent improvements to module-name resolution caching exposed a
problem in the extraction setup.
This commit is contained in:
Matthew Flatt 2019-06-22 07:40:55 -06:00
parent f00de510de
commit 1e84b11462
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
racket/src/expander/run.rkt
View File

@ -6,7 +6,9 @@
[eval host:eval]
[namespace-require host:namespace-require]
[current-library-collection-paths host:current-library-collection-paths]
[current-library-collection-links host:current-library-collection-links])
[current-library-collection-links host:current-library-collection-links]
[current-namespace host:current-namespace]
[make-base-namespace host:make-base-namespace])
compiler/depend
"common/set.rkt"
"main.rkt"
@ -220,7 +222,10 @@
(host:current-library-collection-paths l))
(let ([l (list #f
(build-path checkout-directory "share" "links.rktd"))])
(host:current-library-collection-links l)))
(host:current-library-collection-links l))
;; Need to start with a fresh namespace when we adjust the
;; collection and links paths; otherwise, caching can interfere
(host:current-namespace (host:make-base-namespace)))
(current-library-collection-paths (host:current-library-collection-paths))
(current-library-collection-links (host:current-library-collection-links))