Reprovide all provides from a directory

bennn commented 7 years ago

feature request: reproviding a path-string? that refers to a directory reprovides from all files in the directory.

So if I had a directory dir/ with files a.rkt and b.rkt, then:

#lang reprovide
"dir/" ;; or something like `(all-from-directory "dir/")`

Should be the same as:

#lang racket/base

(require "dir/a.rkt" "dir/b.rkt")
(provide (all-from-out "dir/a.rkt" "dir/b.rkt"))

Typed Racket does something like this here: https://github.com/racket/typed-racket/blob/master/typed-racket-lib/typed-racket/static-contracts/combinators.rkt

AlexKnauth commented 7 years ago

I want to keep it as close to the syntax of require as possible. Would it be okay if instead we made all-from-directory as a normal require-transformer, and allowed using it in #lang reprovide modules?

(Edit: Or to follow the convention of require-transformers, directory-in?)

bennn commented 7 years ago

Yes, directory-in would be good

AlexKnauth commented 7 years ago

What types of files should directory-in try to require? In the example you gave the code only requires files with a .rkt extension, which is fine for a private TR thing, but I'm not sure that's what this should do. Should it instead include all the files which can be read as valid modules, either #lang files or (module ...) s-expressions?

AlexKnauth commented 7 years ago

How should I properly reference the directory relative to the path of the file the way require would? I see a few options:

Relative to (current-directory): really bad, breaks whenever it's compiled from a different directory
Relative to the path given by syntax-source: really bad, breaks when a macro generates it
Somehow use define-runtime-path? I don't know how I would get it to refer to the correct thing...
Somehow use convert-relative-module-path or current-require-module-path: This seems like it should be the Right Way, but convert-relative-module-path is just returning the same path I'm giving it, which ends up behaving just like if I used (current-directory), and current-require-module-path is false within my require transformer.

bennn commented 7 years ago

For types of files, I think .rkt. Maybe .rkt can be the default and directory-in can take an optional suffix. Or maybe (glob-in glob-str) for more freedom (even (glob-in "parent-dir/**/*.rkt"))

(define-runtime-path directory-in-cwd ".") seems best offhand .. maybe syntax-local-lift-module-end-declaration will put it in the right place. I guess another problem is that each use of (directory-in ...) will need to either:

decide whether to add a define-runtime-path, based on some state
create a new define-runtime-path and use a new identifier

I don't know convert-relative-module-path.