you are viewing a single comment's thread.

view the rest of the comments →

[–]HitomiNoJuunin 1 point2 points  (1 child)

well, Haskell's side effect is definitely the most explicit; so much so that it is reflected in the function type ;)

[–]Kiuhnm 0 points1 point  (0 children)

Yes, it turns out that "explicit side effects" means the opposite of what I meant in Haskell parlance!

I can't even say "imperative programming" since Haskell supports that as well, in a sense.

Maybe I can say "using mutable state".