On 4/3/07, Simon Marlow
System.Directory --> new package directory (dep. on filepath, unix/Win32)
Why bother with having hierarchical module names if package names are not similarly qualified? It seems like collisions in the packaging name space are just as likely as in the module name space (especially with single-module packages like many that you proposed). There are multiple competing collection libraries available, and a name like "collections" or "containers" does not really help to differentiate this particular library from the others, or suggest its provenance. Considering that arrays are collections, and the "collections/containers" package depends on Data.Array such that significant modifications to Data.Array will probably cause modifications to the modules in "collections/containers," why not just merge Data.Array into the collections/containers package? Regards, Brian