Re: Export lists in modules

On Thursday 23 February 2006 09:53, Ketil Malde wrote:

Wolfgang Jeltsch writes:

...

...

Personally, I would greatly prefer to have libraries that do not clash with common Prelude functions.

I would solve this problem by reducing the Prelude to just a core. List function could go, for example, (mostly) into Data.List.

If this means that you must import Data.List almost everywhere, this won't change anything - only add yet another import to every file.

But you could import something different instead! For instance, I can then easily replace Prelude stuff with Edison or some other data structure library. That is what the whole discussion is about. I agree with the rest of what you wrote. Ben