mokus at deepbondi.net
Wed Jul 18 17:59:31 CEST 2012
I should probably be more clear - it supports all the same resource limiting mechanisms as Mueval because it uses Mueval (modified to support Safe Haskell).
On Jul 18, 2012, at 11:37 AM, James Cook <mokus at deepbondi.net> wrote:
> The irc server it runs on has about 10 users, all of whom I know and trust, so I have not tested it extensively but it should be as safe as anything else running Safe Haskell. Mueval uses the ghc API and with a minor modification can do so in "safe" mode. As long as you don't trust any packages you shouldn't, it should be fine. This sort of thing is why safe Haskell exists.
> On Jul 18, 2012, at 11:17 AM, Gwern Branwen <gwern0 at gmail.com> wrote:
>> On Wed, Jul 18, 2012 at 11:12 AM, James Cook <mokus at deepbondi.net> wrote:
>>> It diverged from the official version quite a while ago, but it builds on the latest GHC and uses Safe Haskell for the @eval module.
>> That doesn't sound very safe. How does it handle all the DoS attacks
>> etc in the mueval test suite?
>> Haskell-Cafe mailing list
>> Haskell-Cafe at haskell.org
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
More information about the Haskell-Cafe