[racket-dev] proposal: `data' collection

On Jun 23, Sam Tobin-Hochstadt wrote:
> At the Northeastern PLT lunch today, I proposed adding a top-level
> `data' collection, for all manner of data structures.  People here
> thought it was a good idea, so I'm proposing it to the whole group.

(The name sounds iffy to me.)


> Definitely candidates:
>  Hari Prashanth's functional data structure library (which he's been
> working on with me)
>  `unstable/skip-list' (by Ryan)
>  `unstable/interval-map' (by Ryan)
>  `unstable/queue' (by Carl)
> 
> Possible candidates (these would still be provided by `racket' if they
> are currently):
>  `racket/dict'
>  `racket/set'
>  `racket/list'
>  `racket/vector'
>  `unstable/{list,dict,set,hash}'
>  `unstable/sexp-diff'

* I went over one file in unstable, and had a quick look through a few
  others.  Assuming that this will be a fundamental collection, there
  is much work needed to get the unstable stuff to an appropriate
  level.

* Re the functional structures, I'm skeptical about adding a big ball
  of code that was never used.  I'd like it to have more public time
  before it's added.  (Eg, planet.)

* The `racket/*' stuff needs to be where it is since it's part of the
  current core.  (It can still be reprovided through the new
  collection.)  If the definition of the core changes to include the
  new collection, then there are more restrictions on it like not
  depending on typed scheme.  (And this is due to how things are now,
  where typed scheme is not part of the core.)

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