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
> 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
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
3 matches
Mail list logo
