On 03/08/2011 03:23, David Terei wrote:
I think we should setup GHC so that the base library is trusted by
default. I'd like to use the 'Safe' pragma in some of the packages
included with GHC but that relies on base being trusted. Assuming no
objections could someone point out please where in the build process I
need to change so that stage1 has base trusted, stage2 has base
trusted and the installed ghc has base trusted...
Perhaps all packages should be trusted by default? (Perhaps with some
Cabal configuration option to reverse the behaviour). After all,
trusting a package is a no-op unless the package defines some Safe or
Trustworthy modules. If we don't do this, then everyone has to
explicitly type a bunch of 'ghc-pkg trust' commands to avoid compilation
failure with Cabal packages that use Safe or 'import safe'.
Cheers,
Simon
Cheers,
David
On 2 August 2011 11:30, David Mazieres expires 2011-10-31 PDT
<mazieres-cirnxf5cxdpp5eibcyehm72...@temporary-address.scs.stanford.edu>
wrote:
At Tue, 2 Aug 2011 09:04:30 +0000,
Simon Peyton-Jones wrote:
Simon's message yesterday boils down to
"solve the problem using CPP"
Although hardly beautiful, it seems to work and means we don't need
another new feature. Is that acceptable to David& David?
I think we can live with that, as long as all the core libraries are
okay using the CPP extension, which it sounds like they are.
Thanks,
David
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
