## Key points

### Every valid expression is a value

Values are values (e.g., 5). Variables are values. Variables do not hold values; they are values (but with names). Functions are values. Programs are values.

Here are some values.

x = 5

q = let y = x + 10
in y + 3

r = z * x + w
where w = 4
z = 3

f c = c*c

main = do putStrLn (show (f 3))
putStrLn (show r)

Run ghci on the file haskell-quick-intro.hs and type x, q, and r to show the various computed values:

\$ ghci haskell-quick-intro.lhs
GHCi, version 7.8.3: http://www.haskell.org/ghc/  :? for help
[1 of 1] Compiling Main             ( haskell-quick-intro.lhs, interpreted )
*Main> x
5
*Main> q
18
*Main> r
19
*Main> main
hello
9
19
*Main> t
hello
9
19
*Main>


### Variables never vary; they are “bound”

x2 = 55
x2 = 75 -- not gonna work

We can see it’s not gonna work by reloading the file in ghci:

*Main> :reload
[1 of 1] Compiling Main             ( haskell-quick-intro.hs, interpreted )

Multiple declarations of ‘x2’


### Every value has a specific type

Let’s ask ghci about the types of the variables we bound:

*Main> :t q
q :: Integer
*Main> :t x
x :: Integer
*Main> :t q
q :: Integer
*Main> :t r
r :: Integer
*Main> :t f
f :: Num a => a -> a
*Main> :t main
main :: IO ()
*Main> :t t
t :: IO ()
*Main>


### Types are inferred

We didn’t define the type of the function f. It inferred it had to be a -> a where a is one of the number types. Why? Because we used *, which has the type:

*Main> :type (*)
(*) :: Num a => a -> a -> a
*Main>


In other words, it takes two values of type a (i.e., any type, so long as it has parent type Num) and gives back a value of the same type.

### Functions are just partially-realized values

Functions have types like Int -> Int or a -> b -> a (for some types a and b). Any lower-case type, such as a, means “any type can go here.” Of course, when the function is actually executed, if a matches up to type X, all a type values in the function must be type X for that function call.

Give a function one of its several arguments, and it just becomes a “slightly more realized” value. I.e., that argument is replaced with its value everywhere it appears in the function, but the function still is not fully realized. Normal variables, like x above (first example), are simply fully-realized values.

Example of a function:

average_three_values x y z = (x + y + z) / 3.0

Let’s interrogate the types and values:

*Main> :t average_three_values
average_three_values :: Fractional a => a -> a -> a -> a
*Main> :t (average_three_values 8.0)
(average_three_values 8.0) :: Fractional a => a -> a -> a
*Main> :t (average_three_values 8.0 9.0)
(average_three_values 8.0 9.0) :: Fractional a => a -> a
*Main> :t (average_three_values 8.0 9.0 10.0)
(average_three_values 8.0 9.0 10.0) :: Fractional a => a
*Main> let avg2 = (average_three_values 8.0)
*Main> let avg3 = (avg2 9.0)
*Main> let avg4 = (avg3 10.0)
*Main> avg4
9.0


This method of partial application is called currying (after the mathematician Haskell Curry).

### Values are computed lazily (as-needed)

When compiling a binary, execution starts in main. Whatever value main computes, and whatever values that computation depends on, are the only values computed.

So, in this code, y is never computed:

main = let x = 5
y = x * x
in do putStrLn "hello"
putStrLn x

This means you can actually use infinite lists, for example, and never have a problem (unless you try to process the whole list…).

### Side-effects are not allowed

There are only values. In the code x + y, for example, there is no “room” for some random “print” statement or whatever. It would look like x + (putStr "foo") + y, which doesn’t make sense because putStr is not a numeric type (so it can’t be added).

Due to laziness (see previous point), even this never prints anything (if it were even valid code, and it’s not for another reason, see below):

f x = let y = putStr "foo"
in (2+x*x)

That’s because y is never needed, so its value is never computed. Likewise, this does not work:

f x = putStr "foo"
(2+x*x)

This example does not compile because putStr has type (and value) IO () (i.e., void), which does not contribute to any arithmetic computation; it cannot feed into the next value (2+x*x) because (1) (2+x*x) is not a function and (2) if we put a function there, it has to be of special type IO () -> IO a, i.e., it has to accept a void input. Such functions do exist, but they have to be used in a special way; see the next section.

Generally, you can’t put a “print” statement, or anything else with side-effects, in a position where it does not contribute to a computation. You can only do side-effects when using the IO trick (next section).

### IO is a trick

Since Haskell disallows side-effects, as described previously, there has to be some fancy trick to enable a program to read input from the outside world and send output to the screen or elsewhere. This trick is with a “monad.”

The basic idea is that the main function, where everything begins, is given the IO object. Any code that wants to do input/output must use this IO object. The IO object is passed along to each input/output action, in sequence (each action hands it off to the next action). The result of input can be extracted from the IO object, and used in other “pure” computations (which aren’t given the IO object), but the value extraction operation still must exist in a sequence passing along the IO object.

Example:

main = do putStr "Type your name: "
name <- getLine
putStrLn name
putStr "Type a number: "
num_str <- getLine
num2 = num * num + 5
in do putStr "New number: "
putStrLn (show num2)
putStrLn "We're done."

It’s hidden from us (due to the special do syntax), but the IO object is being passed across putStr, putStrLn, and getLine. The let only sets up bindings, it’s not part of the chain.

*Main> :reload
[1 of 1] Compiling Main
*Main> :main
Type a number: 23
New number: 534
We're done.
*Main>


## “Functional programming” is programming with data

In functional programming, every operation transforms or generates data. There are no operations (except the IO trick) that simply perform actions for the sake of producing side effects (e.g., modifying memory, launching missles, inserting into or querying databases, etc.).

[Of course, with the IO trick, we really can produce side-effects and launch missiles, or whatever. But the program is still “pure” because it acts as if these side-effects are actually just “values” that will be the same every time the program runs.]

• There are no loops. A loop means “do something X times.” That is not a data transformation or generation operation; it is an operation that is intended to produce side-effects.

• There is no way to “break” out of a function (nor a loop, because there are no loops). Functions turn into values; if you want the function to finish, just ensure it results in the appropriate value at the appropriate time.

• Conditionals must always have an “else” value; if they didn’t, what would be the value of the conditional when the if part is false? Remember, every expression must turn into a value.

• There are no pointers and no mutable arrays. All function calling is call-by-value; a function always receives a copy of each of its arguments.

Except for (minimal) IO code, functional programs play with data. Functional programs are not composed of “statements” but rather they are composed of data manipulations. Every output of a function is the input to another function.

## Lists are a crucial data structure

Often, we have lots of data. Often, these data are collected into lists. Not surprisingly, there exist many simple functions that play with lists. The main functions are:

• map: apply a (unary) function to every element in the list, resulting in a new list

• filter: drop elements from the list according to a (unary) function; when that function returns false for some element, the element is left out; a new list results

• foldr: “fold” a list by applying a (binary) function to the first and second element, then the result of that with the third element, the result of that with the fourth element, etc., resulting in a single value. (foldr means fold-to-the-right; there is foldl, too).

You can also pull apart the head and tail when binding:

let (x:xs) = [1, 2, 3, 4, 5]
in ...

In that code, x is 1, xs is [2, 3, 4, 5].

Examples of map, filter, and foldr:

xs = [1, 3, 5, 2, 6, 2, 5, 8]

my_mapping_fn n = 2*n

xs2 = map my_mapping_fn xs

my_filtering_fn n = (n mod 2 == 0)

xs3 = filter my_filtering_fn xs

my_foldr_fn m n = (m * n + 5)

-- foldr needs three arguments: the folding fn, an initial value (for
-- the first folding fn call), and the list
xs4 = foldr my_foldr_fn 10 xs

Here are their values:

*Main> :reload
[1 of 1] Compiling Main             ( haskell-quick-intro.hs, interpreted )
*Main> xs
[1,3,5,2,6,2,5,8]
*Main> xs2
[2,6,10,4,12,4,10,16]
*Main> xs3
[2,6,2,8]
*Main> xs4
155950
*Main>


### “List comprehensions” generate new lists

It’s often very convenient to generate a new list simply by describing what it would look like. Examples:

*Main> [x | x <- [1..3]]
[1,2,3]
*Main> [y*2 | y <- [1..5]]
[2,4,6,8,10]
*Main> [y*2+x | y <- [1..5], x <- [4, 2, 6, 2]]
[6,4,8,4,8,6,10,6,10,8,12,8,12,10,14,10,14,12,16,12]
*Main> [(x,y) | x <- [1..5], y <- [1..5], x < y]
[(1,2),(1,3),(1,4),(1,5),(2,3),(2,4),(2,5),(3,4),(3,5),(4,5)]
*Main> [x | x <- [q | q <- [1..5]]]
[1,2,3,4,5]
*Main>


### Other list functions

• ++: append two lists: xs ++ ys

• head: get the head of a list

• tail: get the tail of a list

• length: get the length of a list

• reverse: reverse a list

• !!: get the nth element: xs !! 3

• take, drop: keep or drop a certain number of values

• splitAt: split a list into two at a certain position

Many more list functions are available in the Prelude, i.e., Haskell’s standard library.

## Examples

### Quicksort

quickSort []     = []
quickSort (x:xs) = quickSort [a | a <- xs, a < x]   -- Sort the left part of the list
++ [x] ++                        -- Insert pivot between two sorted parts
quickSort [a | a <- xs, a >= x]  -- Sort the right part of the list

## Useful libraries

Just a sample, obviously.

• Yesod – A spiffy web framework for building large web apps in Haskell. Among other cool features: SQL injections are impossible, due to Haskell’s strong type system. Broken (internal) links are also impossible.

• QuickCheck – Generates random test inputs, based on the types of the parameters, and when tests fail, automatically narrows down the failing example to a (nearly) minimal failing case.

• Persistent – Database library (SQL databases, et al.).

• Shakespearean Templates – HTML, CSS, JavaScript template libraries.

• Conduit – Efficient handling of streams large and small, of all varieties (console IO, network IO, binary file IO, etc.).

• OpenGL – See link for other game stuff as well.
{"extraction_info": {"found_math": true, "script_math_tex": 0, "script_math_asciimath": 0, "math_annotations": 0, "math_alttext": 0, "mathml": 0, "mathjax_tag": 0, "mathjax_inline_tex": 0, "mathjax_display_tex": 0, "mathjax_asciimath": 1, "img_math": 0, "codecogs_latex": 0, "wp_latex": 0, "mimetex.cgi": 0, "/images/math/codecogs": 0, "mathtex.cgi": 0, "katex": 0, "math-container": 0, "wp-katex-eq": 0, "align": 0, "equation": 0, "x-ck12": 0, "texerror": 0, "math_score": 0.4431704580783844, "perplexity": 3718.029036339361}, "config": {"markdown_headings": true, "markdown_code": true, "boilerplate_config": {"ratio_threshold": 0.18, "absolute_threshold": 10, "end_threshold": 15, "enable": true}, "remove_buttons": true, "remove_image_figures": true, "remove_link_clusters": true, "table_config": {"min_rows": 2, "min_cols": 3, "format": "plain"}, "remove_chinese": true, "remove_edit_buttons": true, "extract_latex": true}, "warc_path": "s3://commoncrawl/crawl-data/CC-MAIN-2018-47/segments/1542039743732.41/warc/CC-MAIN-20181117185331-20181117211331-00420.warc.gz"}