Submodules declared with `module+` are spliced together:
http://docs.racket-lang.org/reference/module.html?q=module%2B#%28form._%28%28lib._racket%2Fprivate%2Fbase..rkt%29._module%2B%29%29
So it is a (loose) convention to write
(module+ test
(require rackunit))
at the top of the file, with the ot
Thanks for the feedback. I should be able to apply all of these in the
next day or two.
Regarding the test module and rackunit, the raco package template
actually puts two test modules into main.rkt, with rackunit in one of
them. This smells like a mistake, right? I'm going to try to find the
rele
On Sunday, August 27, 2017 at 7:57:52 PM UTC-7, Royall Spence wrote:
> And it's ready to consume:
> https://pkgd.racket-lang.org/pkgn/package/dotenv
>
> This is the first Lisp-family code I've published, so that's exciting.
> Any feedback the list has to offer regarding style, approach, or
> packa
And it's ready to consume:
https://pkgd.racket-lang.org/pkgn/package/dotenv
This is the first Lisp-family code I've published, so that's exciting.
Any feedback the list has to offer regarding style, approach, or
packaging would be welcome.
On Sun, Aug 27, 2017, at 10:09 PM, 'Royall Spence' via Ra
Thanks, Jack. It sounds like a great Rackety solution and easy way to
get into trying my own languages. I've already started work, though, and
the 40 lines of code I've written looks like it'll do the job once I
shake out the bugs.
On Sun, Aug 27, 2017, at 05:49 PM, Jack Firth wrote:
> On Sunday,
5 matches
Mail list logo