@krismicinski I believe the answer is no

thanks for letting me know!

why is a module-path not allowed to be an absolute path?

e.g. (module-path? "foo.rkt") => #t but (module-path? "/foo.rkt") => #f

Presumably to discourage/avoid accidentally making a module depend being on a particular person’s computer. You can always override it by using (file "/some/absolute/path.rkt"), instead.

(i realize i may be betraying a lack of understanding of some module fundamentals—it me)

ah interesting

oh, but apparently not if i’m doing dynamic-require…

> (dynamic-require (file "/tmp/test.rkt") ''x)
; stdin:5:17: file: misuse of module-path constructor (not within, e.g.,
;   `require' or `provide')

You need '(file "/tmp/test.rkt"), since dynamic-require takes an expression, and file is syntax.

oh perfect, thanks. (i swapped that and had the extra quote on the provided arg)