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

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.

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