summaryrefslogtreecommitdiffhomepage
path: root/haskell.html.markdown
diff options
context:
space:
mode:
authorAdam <adam@adambard.com>2013-07-03 23:01:47 -0700
committerAdam <adam@adambard.com>2013-07-03 23:01:47 -0700
commit8b536513d786d79fd95b7b0eb6a505dc71ed9604 (patch)
tree21706a615ba947bcb82a3bcd550fc93279aae439 /haskell.html.markdown
parent9ad61b5586993bda1eebd70a8dd4c721db83a396 (diff)
Edit for line length
Diffstat (limited to 'haskell.html.markdown')
-rw-r--r--haskell.html.markdown16
1 files changed, 8 insertions, 8 deletions
diff --git a/haskell.html.markdown b/haskell.html.markdown
index 4d5ce642..11109ab8 100644
--- a/haskell.html.markdown
+++ b/haskell.html.markdown
@@ -367,14 +367,14 @@ main'' = do
putStrLn result
putStrLn "This was all, folks!"
--- The type `IO` is an example of a "monad". The way Haskell uses a monad to do IO allows it to
--- be a purely functional language. Any function that interacts with the outside world (i.e. does IO)
--- gets marked as `IO` in its type signature. This lets us reason about what
--- functions are "pure" (don't interact with the outside world or modify state)
--- and what functions aren't.
-
--- This is a powerful feature, because it's easy to run pure functions concurrently
--- so concurrency in Haskell is very easy.
+-- The type `IO` is an example of a "monad". The way Haskell uses a monad to
+-- do IO allows it to be a purely functional language. Any function that
+-- interacts with the outside world (i.e. does IO) gets marked as `IO` in its
+-- type signature. This lets us reason about what functions are "pure" (don't
+-- interact with the outside world or modify state) and what functions aren't.
+
+-- This is a powerful feature, because it's easy to run pure functions
+-- concurrently; so, concurrency in Haskell is very easy.
----------------------------------------------------