[racket-dev] okay to require rackunit in modules required at startup?

On Jun 28, 2011, at 10:52 PM, Eli Barzilay wrote:

> An hour and a half ago, John Clements wrote:
>> In certain places, I know that we're trying to be careful to
>> minimize 'require's that occur as part of DrRacket startup.  Is
>> 'rackunit' something we're trying to avoid? Specifically, I have old
>> unit tests in collects/stepper/private/shared.rkt that I'd like to
>> revive as rackunit tests.
> 
> Adding this is a bad idea -- but size is not the problem -- the
> redundant dependency is.

The word "redundant" suggests that it's already required... either you meant something like "extraneous", or else I just plain misunderstood. Can you give me another sentence or two?

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4624 bytes
Desc: not available
URL: <http://lists.racket-lang.org/dev/archive/attachments/20110628/c4da8060/attachment.p7s>