Why the Prelude must die
lennart at augustsson.net
Tue Mar 27 03:21:03 EDT 2007
I agree, I think this is what we need.
Plus a decision of what names the builtin syntax refers to,
like the type of 'a'.
On Mar 26, 2007, at 23:30 , Ashley Yakeley wrote:
> Sebastian Sylvan wrote:
>> The solution is simple:
>> * If there is a "module M where" clause in the beginning of the file,
>> then it's a "proper" module and shouldn't import the Prelude.
>> * If there is no module declaration then it's a "quick'n dirty
>> and should have the Prelude implicitly imported.
>> * Interactive interpreters should probably import the Prelude.
>> That should take of most issues.
> I think this is ideal. I've always thought writing "import Prelude"
> was a good idea if one wants one's module to import the Prelude.
> It's one less corner case.
> Ashley Yakeley
> Libraries mailing list
> Libraries at haskell.org
More information about the Libraries