News for hackers. Stuff that matters.
Re:Testable IO in Haskell by pron on Sunday June 21, 2015 @03:23AM (#9752537)
Yep, it's also great that we can enlist the runtime's help to do the same thing in Java (or any other JVM language) and support use of third-party libraries (the Haskell approach places a pretty severe burden on the code) and make it even more airtight (IIANM you can't prevent unsafePerformIO): We just disable IO by enabling the security manager with a "no-IO" policy[1]. So it's less intrusive, more widely applicable and more airtight than the Haskell approach.

True, the security manager does not limit access to the random-number generator, but this, too, can be done with an extra bit of one-time effort, by injecting a security check into the random number generator's seed generation method (we still want to allow fixed seeds like StdGen).

[1]: Or a finer-grained policy of "no IO except for logging".

Re:Testable IO in Haskell by chongli on Sunday June 21, 2015 @07:18AM (#9752969)
An application which does "no IO" does nothing other than make the computer get hot. Why even run it?
Re:Testable IO in Haskell by pron on Sunday June 21, 2015 @09:27AM (#9753343)
Why, for testing. The calls to IO are replaced with calls to mocks which are then used to verify IO behavior. It's like replacing the IO monad with a type that doesn't actually do IO, only it doesn't require the code to change, so it works even for third-party code.

You can then use the security manager during the test to verify that all IO calls are indeed mocked.