Well, GHC.Exts currently exports the names needed for GHC extensions. The manual entry says that IsString is exported by GHC.Exts.
I have no objection to deprecating GHC.Exts in favour of imports from here and there. Perhaps that is in line with more explicit language pragmas. But if we are going to do that it'd be good to make the policy explicit; to make sure the user manual lines up; and to see what other things we can no longer export (presumably deprecate for now) from GHC.Exts. In short, I'd be content with a change if that's the consensus. S | -----Original Message----- | From: Ian Lynagh [mailto:[EMAIL PROTECTED] | Sent: 03 May 2007 13:45 | To: Simon Peyton-Jones | Cc: [email protected] | Subject: Re: patch applied (packages/base): Add IsString to exports of GHC.Exts | | On Thu, May 03, 2007 at 12:36:29AM -0700, Simon Peyton-Jones wrote: | > Wed Feb 21 02:42:49 PST 2007 [EMAIL PROTECTED] | > * Add IsString to exports of GHC.Exts | | What's the rationale here? Shouldn't we be encouraging people to import | IsString from the portable Data.String? | | | Thanks | Ian _______________________________________________ Cvs-libraries mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-libraries
