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

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.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!