Difference between revisions of "Infrastructure/Utrecht-Hacking-Notes"
Jump to navigation
Jump to search
DonStewart (talk | contribs) |
DonStewart (talk | contribs) |
||
| Line 6: | Line 6: | ||
* https://patch-tag.com/r/dons/containers/home |
* https://patch-tag.com/r/dons/containers/home |
||
| + | |||
| + | Added test suite and coverage data: |
||
| + | |||
| + | * http://code.haskell.org/~dons/tests/containers/hpc_index.html |
||
| + | |||
| + | Added benchmarking suite: |
||
| + | |||
| + | * |
||
| + | |||
| + | Improved performance: |
||
| + | |||
| + | * |
||
=== hackage 2 === |
=== hackage 2 === |
||
Revision as of 07:49, 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:
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?
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.