# Imperative programming vs Functional programming – a Beginner’s approach Part 3: Reduce 1. Introduction

Computer programming is about solving problems and getting things done the right way. However, as a beginner, you don’t care how you do it as long as you get it done. It works so why bother tackling it in a completely different way after all?

I thought the same way when I first stumbled upon functional programming in Swift. I knew about functional programming languages like Haskell or Scala, but I was under the impression that they are only good for research at an academic level and have no practical value of any kind. So I approached it reluctantly at first and soon asked myself how I lived without it.

The biggest challenge you face when discovering new programming paradigms is changing the way you think. This can be scary at first because you are used to doing things in a certain way and now you suddenly feel overwhelmed. It takes time and patience to get used to anything new but it’s worth doing it in the long run – being able to choose the right technique for a certain problem is a skill that any software developer should have in his toolbox.

OK, enough talking – let’s see what functional programming is all about.

2. The imperative approach

Your task for this tutorial is an easy one: compute the sum of the elements in an array. Before diving into coding, think how you would solve the problem and break it into steps. This is how I would do it:

• create the array and populate it with default values;
• create the sum variable and assign its initial value;
• loop through the array and do two things for each iteration:
• extract the current value from the array;
• add it to the sum;
• print the sum to the console;

That’s it for the algorithm – let’s move on to the implementation.

3. The imperative implementation

Fire up Xcode and open a playground. Delete everything from it and add this line to kick things off:

`let array = [1, 2, 3, 4, 5]`

This creates the constant array and assigns its default values.

Note: There are many different ways of creating arrays in Swift – this is the easiest approach of all because it uses type inference to determine the array’s type – Int in this case.

Next create the sum variable and assign its initial value:

`var sum = 0`

This line creates a variable for the sum – it is variable because you are going to change its value soon.

Note: There are many different ways of creating variables in Swift – this is the easiest approach of all because it uses type inference to determine the variable’s type – Int in this case.

Now loop through the array with the for in control flow statement:

```for value in array {

}
```

Note: There are many ways of looping in Swift – this is the best approach for arrays because it gives you access to the current value for each iteration.

There is only one thing you should do inside the for loop for each value of the array – add it to the sum:

`sum += value`

Note: You could also do it like this – the initial approach is shorter because it uses the addition assignment operator:

`sum = sum + value`

Finally, print the sum to the console:

`print(sum, terminator: "")`

Note: There are other ways to print to the console as well – this approach doesn’t print the newline “\n” character in the playground.

That’s it – time for your next challenge: calculate the product of the elements in an array.

4. The imperative implementation revisited

First create the product variable and assign its initial value:

`var product = 1`

Next loop through the array:

```for value in array {

}
```

Now multiply the product by the value:

`product *= value`

Note: You could also do it like this – the initial approach is shorter because it uses the multiplication assignment operator:

`product = product * value`

Finally, print the product to the console:

`print(product, terminator: "")`

That’s it – let’s compare the two implementations.

5. The imperative implementation analysed

Both implementations are similar:

• create the result variable and assign its initial value;
• loop through the array;
• extract the current value;
• modify the result with it;
• print the result to the console;

There are only two major differences between them – the result’s initial value is either 0 or 1 and the operation’s type is either addition or multiplication.

Note: You could refactor the whole thing in two ways:

• update both the sum and the product with the array’s current value in the same loop (Download);

Both approaches avoid code redundancy and respect the DRY (do not repeat yourself) principle, but they don’t deal with the boilerplate code that is common for both implementations. Functional programming to the rescue!

6. The functional approach

Functional programming is about focusing only on what changes and not caring about what stays the same. The only thing that varies between the two previous implementations is the logic that reduces the array’s elements to a certain value, so this is the only thing you have to worry about.

The reduce function does exactly this: it computes a value from the elements of an array based on a certain type of operation.

Enough theory – let’s see the reduce function in action!

7. The functional implementation

Add this line to the playground to get started:

`let sumf = array.reduce(0, combine: +)`

The reduce function has two parameters – the initial value and the operation’s type.

Note: The function’s prototype can be written in many other ways in Swift – this is the simplest approach of all because it uses default operators for its arguments.

Now print the sum to the console:

`print(sumf, terminator: "")`

That’s it – it can’t get any simpler than that! Let’s use the reduce function some more.

8. The functional implementation revisited

Calculate the product of the elements in an array:

`let productf = array.reduce(1, combine: *)`

Now print the product to the console:

`print(productf, terminator: "")`

That’s it – let’s compare the two implementations.

9. The functional implementation analysed

Both implementations are similar – define the initial value and the operation’s type and let the reduce function do the rest – no more boilerplate code.

Note: You could refactor the whole thing by encapsulating the algorithm in a function of its own to avoid code redundancy and respect the DRY principle (Download).

10. Imperative vs functional comparison

• clear steps
• easy to understand

• boilerplate code

• no boilerplate code
• short and sweet