@sanchom The default set of bindings available in a module is determined by the module language, so if your reader produces a module of the shape (module m my/foo/lang ....), then the contents of that module will be expanded in a context where all the exports from my/foo/lang are in scope. That is only relevant for the code actually produced by the reader, though—macro hygiene ensures that if a macro defined in one module is used in another module, it will still refer to the bindings that it did in its original module.

There isn’t anything special about racket/base, it’s “just another language”.