Difference between revisions of "Infrastructure/Utrecht-Hacking-Notes"
Jump to navigation
Jump to search
DonStewart (talk | contribs) |
DonStewart (talk | contribs) |
||
Line 5: | Line 5: | ||
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: |
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: |
||
− | + | * https://patch-tag.com/r/dons/containers/home |
|
=== hackage 2 === |
=== hackage 2 === |
||
Line 11: | Line 11: | ||
Ready Hackage 2 for use. |
Ready Hackage 2 for use. |
||
− | + | * Basic docs: http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/Architecture |
|
− | + | * http://code.haskell.org/hackage-server |
|
=== network === |
=== network === |
Revision as of 06:34, 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:
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
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.