Difference between revisions of "Infrastructure/Utrecht-Hacking-Notes"
DonStewart (talk | contribs) |
DonStewart (talk | contribs) |
||
| Line 7: | Line 7: | ||
* https://patch-tag.com/r/dons/containers/home |
* https://patch-tag.com/r/dons/containers/home |
||
| − | Added test suite and coverage data |
+ | Added test suite and coverage data, (increased coverage to > 50%) |
* http://code.haskell.org/~dons/tests/containers/hpc_index.html |
* http://code.haskell.org/~dons/tests/containers/hpc_index.html |
||
Revision as of 09:35, 28 August 2010
Notes from Utrecht on future directions for packages and infrastructure
containers
Work underway to do general performance improvements to the containers package, based on worker/wrapper and other idioms. New repository for work on patch-tag:
Added test suite and coverage data, (increased coverage to > 50%)
Investigate certain functions, then determine if anything on Hackage uses them. If no such package is found using the Map function, remove it from the API -- 20 years and 2000 packages should be enough empirical evidence.
Added benchmarking suite:
Improved performance:
hackage 2
Ready Hackage 2 for use.
- Basic docs: http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/Architecture
- http://code.haskell.org/hackage-server
- http://sparky.haskell.org:8080/
network
network package is low level, difficult to maintain and fragile. Rewrite using design from python?
hashmaps
Based on Patricia trees and using MurmurHash.
hashtables
Fast, open addressed hashtables: useful, but relatively small ROI. Also quite complex.
text
Propose text for the HP.
platform
Generate unified docs for the HP.