Good call, I'll add a note to the effect. Btw in case it wasn't clear from my response, using #lang cli shouldn't affect the existing workflows that you mentioned, although, you would probably want to define the command line component of your code as a separate #lang cli module, rather than in a module+ main.
On Sun, Jul 25, 2021 at 12:21 PM D. Ben Knoble <[email protected]> wrote: > > Right, thank you for bringing that up. I should have mentioned that the > #lang provides all of racket/base at the module level, so you can write > normal Racket code (including `require`), and any imports at the module > level would be available within the `program` body since it compiles down > to a normal function. > > > > You can also use `provide`, so once you define your command using > `program`, you can provide it the same as any function. The client module > requiring your command would need to be a #lang cli module (at least at the > moment) so that it can actually run the imported command using `run`. > > That would be good to add to the docs in my opinion. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CACQBWFmbq1bPs4-66mkxCVVC9Ob6EJ7ovw-3%3D%2B%3DuBd2ZexGBcA%40mail.gmail.com.
