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

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.

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/c867ee91/attachment.p7s>