A program can be both purely functional, *and* have side-effects. See Haskell, a... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		amelius on May 18, 2015 \| parent \| context \| favorite \| on: Once you go functional, you can never go back 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...

seanmcdirmid on May 18, 2015 [–]

If an effect is explicit, is it still correct to call it a "side" (implicit) effect?

dllthomas on May 19, 2015 | [–]

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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact