News for hackers. Stuff that matters.
Re:Once you go functional, you can never go back by amelius on Monday May 18, 2015 @09:39AM (#9564316)
A program can be both purely functional, and have side-effects. See Haskell, and in particular, see [1].

[1] Tackling the awkward squad: monadic input/output, concurrency, exceptions, and foreign-language calls in Haskell, Simon Peyton Jones, http://research.microsoft.com/en-us/um/people/simonpj/papers...

Re:Once you go functional, you can never go back by seanmcdirmid on Monday May 18, 2015 @10:12AM (#9564506)
If an effect is explicit, is it still correct to call it a "side" (implicit) effect?
Re:Once you go functional, you can never go back by dllthomas on Monday May 18, 2015 @08:33PM (#9567610)
Execution of Haskell has side effects, although they are left unspecified defined by the language. Memory is used, heat is emitted...

I agree that explicit effects should not be called "side" effects.