Proposal: Reserved module namespace for packages on Hackage

Isaac Dupree isaacdupree at
Mon Aug 18 20:03:41 EDT 2008

David Menendez wrote:
> Implementation costs are minor.

There is a serious cost: Sometimes another package is 
*supposed to* provide the same interface, including the same 
module names (e.g. forks or reimplementations.  e.g. SOE). 
If Hackage rejected them, we would have a serious problem 
once people started depending on any package using a Lib. name.

But it's not hard to pretty much avoid conflicts; you don't 
even need the Lib. prefix, you can just use the package name 
as your top-level module name. (right? or does hackage 
arbitrarily reject some module names?)


More information about the Libraries mailing list