racket/collects/data
Matthew Flatt 054a52f547 data/bit-vector: change implementation to fxvectors
There are minor benefits to using fxvectors instead of vectors:
the GC knows that an fxvector has no pointers inside, and the
bytecode compiler knows that `fxvector-ref' produces a fixnum.

BTW, a benefit of fxvectors over byte strings is the lack of an
indirection internally. (Unlike a byte string, the content of
an fxvector is "inlined" into the vector object.)
2012-11-27 07:26:39 -07:00
..
scribblings data/bit-vector: some adjustments for consistency 2012-11-27 07:26:39 -07:00
tests moved the docs-complete library into rackunit 2011-05-05 16:10:42 -05:00
bit-vector.rkt data/bit-vector: change implementation to fxvectors 2012-11-27 07:26:39 -07:00
gvector.rkt add #:break' and #:final' to `for' forms 2012-09-14 14:57:35 -06:00
heap.rkt add heap sequencing fns to data/heap 2012-10-27 21:09:29 -04:00
info.rkt Some info.rkt cleanups. 2011-08-29 16:33:13 -04:00
integer-set.rkt Move mzlib/integet-set => data/integer-set 2012-07-20 16:00:47 -04:00
interval-map.rkt removed useless requires 2011-09-27 19:28:44 -06:00
order.rkt Implementation of #:defaults keyword for define-generics 2012-11-09 20:14:56 -05:00
queue.rkt extend data/queue library 2012-11-21 11:10:02 -06:00
skip-list.rkt Rename generics => generic. 2012-05-24 16:51:14 -04:00
splay-tree.rkt Rename generics => generic. 2012-05-24 16:51:14 -04:00