Anonymous functions originate in the work of Alonzo Church in his invention of the lambda calculus in 1936, before electronic computers, in which all functions are anonymous.[2] In several programming languages, anonymous functions are introduced using the keyword lambda, and anonymous functions are often referred to as lambdas or lambda abstractions. Anonymous functions have been a feature of programming languages since Lisp in 1958, and a growing number of modern programming languages support anonymous functions.

Lambda comes from the Lambda Calculus and refers to anonymous functions in programming. Why is this cool? It allows you to write quick throw away functions without naming them. It also provides a nice way to write closures. With that power you can do things like this.

So let's stress out and repeat again what we have found and confirmed about what lambda is:

lambda -> anonymous function.

lambda calculus -> computations expressed as math functions.

lambda -> alonzo church represents a function with this greek letter.

map

If you tell a non FP developer, "hey I just wrote a function and I named it map what do you think it's doing?". He might answer, "maybe something with google maps?" . Well actually you could name map traverse or something like that the thing is that if FP is closely related to functional programming, and functional programming is closely related to math then we had better stick with the mathematical terms as awuful and non descriptive as they are.

In our case map is actually a good name, it's mapping from one item on our source structure to another item in our destination structure. you cannot really deduce from the name only that the destination structure has the same shape as the source structure, but if you talk to mathematician he can deduce it, and we love mathematician's deductions, The great book Scala Design Patterns By Ivan Nikolov says:

Following common conventions would make things much simpler

and this is exactly what the map name is all about.

Do you write loops? you do this all day right? Do you write loops that convert each item in a list into another? well map is exactly that, nothing special here, you do this all day.

map - are you iterating something and applying a function to ieach item?. are you looping too much? maybe all the stuff you are looping on can inherit from something? let them inherit from map.

In many programming languages, map is the name of a higher-order function that applies a given function to each element of a list, returning a list of results in the same order. It is often called apply-to-all when considered in functional form.

well so we have map which iterates something and applies a function but wikipedia says:

map for scala list:

finaldefmap[B](f: (A) ⇒ B): List[B]

First question comes to mind, we have just defined map to take a type parameter [B] but what about type parameter [A] why didn't we define it also?

Well, if you look at the definition of List trait itself you would see that [A] is the type of the list, so it's already defined.

Practice

Complete the signature of the below map function

1

2

3

4

5

6

7

packagecom.part01

traitMyList[A]{

defmap[B](f: (A)=>B): MyList[_]= ??? // Replace the _ with the type you think the output MyList[_] should be.

}

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

More on map

to define map in haskell on list which is denoted by [] , you do the below which let's you see the whole picture in a very compact way.

map :: (a -> b) -> [a] -> [b]

so we have an input function from a to b and we transform list [a] to list [b] now you see why haskell is more compact and much easy to lern FP concepts, I told you. But once you get the hang of scala it's rather good also.

Now in almost all languages you can see the same thing, transforming from one kind of element to another and the shape stays the same for you.. for exmaple in ruby

[1,2,3,4].map {|i| i + 1}
# => [2, 3, 4, 5]

in closure:

(map #(+ % 1) [1 2 3 4])
;; => (2 3 4 5)

So we just take each element apply the map higher order function which takes another function, and it does it's mapping over the list and returns us a new list or the same object of the same type.

Conclusion

I think we have covered the basics terms here, map, lambda, which gives us the basis for functional programming, we have seen like our first higher order function map which takes another function, which is pretty awesome, in the next post we would continue to functor and friends.

functor

So we have lambda which for our sake is an anonymous function, we have map, which just tells us to go over each item and apply a function, let's get to functor.

You can conclude that standard Scala types such as List, Option, and others that define a map method are functors.

So functor refers to the types which have the map function and that the output structure is same as the original structure.

Do you have things that you can map over and get to the same structure only with different items? you do this all day, this is what a functor is, it's this thing you can map over and get with the same structure to the same structure only with different items.

so as we see it the functor is the thing that has a map function where we have a restriction that the output structure is the same as the input structure. For list we want a list.

FP Impurity

As a final word I would like to talk about FP and impurity.

I know that sounds like an oxymoron but FP has impurity why? because it's a cruel world, you have to do IO. FP has no solution for that. FP will tell you do your pure core as big as you can and wrap that impure stuff with IO, it won't turn it to pure sutff it just wraps it in IO. FP tells you well if you cannot make this function pure at least tell us in it's signature it's impure. We like function signatures in FP.