ha! $ raco expand module-begin.rkt $ raco expand module-begin.rkt (module module-begin racket (#%module-begin (module configure-runtime '#%kernel (#%module-begin (#%require racket/runtime-config) (#%app configure '#f))) (#%require syntax/parse/define) (define-syntaxes (#%module-begin) ...) (module* use #f (quote-syntax (#%plain-module-begin)))))

so it does not begin with #%module-begin

@shu—hung yes, sorry, I wanted to try it and maybe adapt the test before I merged the PR but I haven’t had a chance yet

@mflatt returning to our conversation about module-path-index-join from this weekend, I have another issue

I would like to create a module path that works from a submodule of the place I currently am

given a module path index (or a module path) pointing to a given place

Normally, if the original module path (index) is just foo or "foo.rkt" or (submod "foo.rkt" bar) then just using it directly works fine

but if the original module path is (submod ".." foo) then putting that in a further submodule just doesn’t work

@ryanc I see. Thanks!

@samth If you’re in the module-path-index world, then you can module-path-index-join a (submod "." bar). If you’re in the module-path world and want to stay there, then I don’t know a better approach than looking for submod and adding to the end – that is, partially parsing the module path. (I forgot why allowing nested submod wasn’t trivial in the first place.)

Ok, thanks