Difference between revisions of "Infrastructure/Utrecht-Hacking-Notes"
Jump to navigation
Jump to search
DonStewart (talk | contribs) |
JohanTibell (talk | contribs) |
||
Line 30: | Line 30: | ||
network package is low level, difficult to maintain and fragile. Rewrite using design from python? |
network package is low level, difficult to maintain and fragile. Rewrite using design from python? |
||
+ | |||
+ | === hashmaps === |
||
+ | |||
+ | Based on Patricia trees and using MurmurHash. |
||
=== hashtables === |
=== hashtables === |
Revision as of 07:51, 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?
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.