Difference between revisions of "Infrastructure/Utrecht-Hacking-Notes"

From HaskellWiki
Jump to: navigation, search
 
Line 1: Line 1:
 
== Notes from Utrecht on future directions for packages and infrastructure ==
 
== Notes from Utrecht on future directions for packages and infrastructure ==
   
* containers
+
=== containers ===
   
* hackage 2
 
  +
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:
   
* network
 
  +
* https://patch-tag.com/r/dons/containers/home
   
* hashtables
 
 
=== hackage 2 ===
   
* text
 
  +
Ready Hackage 2 for use.
   
* platform
 
  +
* Basic docs: http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/Architecture
  +
* http://code.haskell.org/hackage-server
   
* haddock
 
 
=== 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.

Revision as of 06:33, 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:

* https://patch-tag.com/r/dons/containers/home

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.