Peter Simons writes:
I'd like to have complementary libraries in there. For instance: I have written a set of QuickCheck combinators, which can be used to generate random expressions to test parsers. If this were to be added to "hslibs", it would probably go to "Debug.QuickCheck.Parser".
Of course, we could add a prefix like "HSLibs" to _all_ libraries included in the repository, to make sure they don't collide with the standard ones, but IMHO this is overkill.
It's also not a guarantee that your libraries won't collide. The only way (currently) to have such a guarantee is to use User.To.Cryp.Simons as the root of your library tree. Perhaps there's a demand for a part of the hierarchy that is a "free for all", with no formal process for acquiring names, where collision is "at your own risk". Suggestions for the root name for this hierarchy are welcome: Unstable or Temp perhaps? Cheers, Simon