On Fri, Jul 13, 2012 at 10:21 AM, Simon Marlow <marlo...@gmail.com> wrote:
> We're still better off than before: currently you have to trust *all* the > code, whereas with Safe Haskell you only have to trust the Trustworthy code. > > Furthermore, nobody is saying that you as a library maintainer or a user > have to audit anything. Only a user that wants to run untrusted code has > to worry about what they're trusting, and Safe Haskell gives them three > things they didn't have before: (a) automatic checking for Safe code, (b) a > way to see which modules have to be trusted, and (c) a mechanism for > telling the system which packages are trusted. > Yes, I see your point now, after reading the docs more carefully. 27% of the packages on Hackage being inferred safe, however, means you might have an uphill battle on your hands :) G -- Gregory Collins <g...@gregorycollins.net>
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
