It might be worth noting that there was a thread on the racket-dev list a little while back that covered a similar topic about submodules and search paths:
https://groups.google.com/d/msg/racket-dev/8BFT-RBDp9E/Y1xOCyf3nIMJ > On Mar 12, 2016, at 10:22, Jay McCarthy <[email protected]> wrote: > > For my taste, I don't want to run any program on my files to "turn > them into real Racket". So, I would not want to do this as a tool. > > On the other hand, I would like to see us unify submodules and > collections into a single concept and have consistent require path > rules. For instance... > > - (require a) currently means (require a/main) > - (require a/b) currently means (require a/b) > > I'd prefer a single consistent rule where if "a/b" exists, it is used, > otherwise "a/b/main" is used, so that "main" is like "index.html" on > the Web. > > Similarly, I would like to unify `(submod a/b c)` to just be `a/b/c`. > > The idea would be that when you see a module path, you search for the > most specific file, so a/b/c would be... > > a/b/c > a/b/c/main > a/b submod c > a submod b submod c > > This would allow a generalization of your tool where a single file > could be any number of Racket modules (rooted in the file's module > path), just allowing a straight-forward "single-file package" concept. > > Jay -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
