[racket-dev] Things we could move out of the core

From: Eli Barzilay (eli at barzilay.org)
Date: Wed Jun 26 01:08:32 EDT 2013

Two.5 notes:

* IMO the sandbox and errortrace should stay in -- even if they're not
  needed, they are both intimately tied to the core so there wouldn't
  be any benefit from moving them to a package.

* I think that it makes sense to move compatibility into its own
  package, and move the mzlib stuff into that same package.

* Maybe the same for data?


9 hours ago, Sam Tobin-Hochstadt wrote:
> While moving some files around between packages, I realized that there
> are a number of things that could be moved out of the core and into
> packages.  Here's a partial list of things that I think are not needed
> at all by the rest of the core:
> 
> - racket/sandbox and the rest of the sandbox code
> - data/{union-find, interval-map, splay-tree, skip-list, order, gvector, heap}
> - srfi/4
> - unstable/{options, contract}
> - errortrace (once sandbox is removed)
> - compatibility/*
> - mzlib/{pconvert, class100, serialize, thread, transcr}
> - a bunch of other parts of mzlib that are just reprovides
> 
> The following are libraries that could be removed with (I believe)
> small changes to the rest of the core:
> 
> - rackunit
> - srfi/13
> - mzlib/unit200 (maybe, this might be hard)
> - mzlib/kw
> 
> If this seems like a good idea to people, I'm happy to go ahead and
> start doing the work.

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

Posted on the dev mailing list.