stefan kersten schrieb:
uvector is pretty bit-rotted in comparison to vector at this point, and it's really seeing no development, while vector is The Shiny Future. Roman, would you call the vector library good enough to use in production at the moment?
i've been using the library for wavelet transforms, matching pursuits and the like,
Nice I have also worked on this topics, even with Haskell. However, at that time I used plain lists.
and while my implementations are not heavily optimized, they perform reasonably well (no benchmarking done yet, though). the key arguments for using vector instead of uvector were the cleaner interface and Data.Vector.Storable for interfacing with foreign libraries (such as fftw, through the fft package).
Btw. Data.StorableVector can also be used for this interfacing, and I would be very interested in an interface to FFTW. Actually, I have already used FFTW on StorableVector http://code.haskell.org/~thielema/morbus-meniere/src/StorableVectorCArray.hs There is also Data.StorableVector.Lazy which is nice for processing stream data.