On Tue, Oct 17, 2017 at 10:02 PM, Alexis King <lexi.lam...@gmail.com> wrote: > > > 1. The issue with module language imports still seems hopeless.
It wouldn't solve the problem with shadowing `require`d identifiers, but would having `#%module-begin` introduce the `require` (with proper lexical context information), instead of doing it with the reader, solve at least this part of the problem? Furthermore, making this change in the reader causes serious issues when > using `hackett` as a module language explicitly, not as a `#lang`. This > is not common when writing most modules, since modern Racket style is to > always use `#lang`, but module languages still crop up when defining > submodules. This means a user defining a submodule with `hackett` as the > module > language with have to manually insert the `require`, since there is no > reader control to introduce it implicitly. This is a wart I have not yet > been able to resolve. -- 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 racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
