Hello Justin,
Thursday, October 4, 2007, 1:47:00 AM, you wrote:
Which could be stripped off it you wanted:
evilDictatator :: a
evilDictator = runUnsafe $ launchMissiles
just imagine using ByteString library with all these runUnsafe calls
flying around :))) or using immutable arrays -
One of the holes in real-world Haskell is you never know if a
library/function is calling unsafePerformIO and you have to trust the
library author. I recognize the necessity of the function, but should it
announce itself? unsafePerformIO has this type:
unsafePerformIO :: IO a - a
Would there
On 10/3/07, Victor Nazarov [EMAIL PROTECTED] wrote:
But how would you know that evil dictator uses unsafePerformIO???
You don't. unsafePerformIO can't be taken it away (there are legitimate
reasons to strip IO), which is why I wonder if it's useful at all.
p.s. CC'ed to haskell-cafe
On Wed, 2007-10-03 at 14:47 -0700, Justin Bailey wrote:
One of the holes in real-world Haskell is you never know if a
library/function is calling unsafePerformIO and you have to trust the
library author. I recognize the necessity of the function, but should
it announce itself? unsafePerformIO
On 10/4/07, Justin Bailey [EMAIL PROTECTED] wrote:
On 10/3/07, Victor Nazarov [EMAIL PROTECTED] wrote:
But how would you know that evil dictator uses unsafePerformIO???
You don't. unsafePerformIO can't be taken it away (there are legitimate
reasons to strip IO), which is why I wonder if
