# Why do functional languages disallow reassignment of local variables?

Fair warning: I don't actually know a functional language so I'm doing all the pseudocode in Python

I'm trying to understand why functional languages disallow variable reassignment, e.g. x = x + 1. Referential transparency, pure functions, and the dangers of side effects are all mentioned, but the examples tend to go for the low-hanging fruit of functions that depend on mutable globals, which are also discouraged in imperative languages.

My question involves variables created and mutated within the function. For example:

def numsum1(n):
sum = 0
i = 1
while i <= n:
sum = sum + i
i = i + 1
return sum


The functional way of doing this seems to be tail recursion, where the updated sum and i are passed from function call to function call. I know that there are existing higher-order functions for this, but I think this illustrates the similarity to numsum1 more plainly:

def numsum2(n): return numsumstep(0, 1, n)

def numsumstep(sum, i, n):
if i <= n:
return numsumstep(sum + i, i + 1, n)
else:
return sum


numsum1 and numsum2 do the exact same thing (with tail call optimization) and are both referentially transparent. I do see why numsum1 is internally referentially opaque; the expressions i + 1 and sum + i change in value with each iteration and thus cannot be replaced by a constant value. But why does that matter if numsum1 itself is referentially transparent? Are there examples of functions that become referentially opaque solely because of reassigning local variables?

• "Each iteration" is the key. sum and i are initialized to a value on entry to the function call, and cannot be changed in that scope. Aug 16, 2021 at 13:55
• No "reassignment" occurs, because i in one call is a completely separate variable from i in another. Aug 16, 2021 at 13:57
• numsum1 is not referentially transparent, as knowing the values of sum and i in the scope of numsum1 depends on knowing how many times the loop has iterated so var. numsumstep is transparent because you only need to know the values passed to a particular call. Aug 16, 2021 at 14:18
• Are you sure this is the right venue for this question? This is computer science not software engineering. In CS theory terms FP is the way it is because there isn't (AFAIK) any formal model for side-effects, which is completely different from what makes FP attractive to e.g. industry programmers. And you picked one of the worst possible languages for illustrating your point: Python has abysmal support for FP both in terms of syntax and community idioms, so the fact that the FP style seems un-idiomatic compared to the imperative version in Python hardly adds any value Aug 16, 2021 at 17:55
• @Jared Smith I did weigh the computer science and software engineering stackexchanges but no source let me make an unambiguous decision. There seemed to be more questions about functional programming here, so I asked it here. Aug 16, 2021 at 18:12

In a pure functional programming language, there is no real notion of time at all. So, saying that a variable x has value a at one point and then b later simply doesn't make any sense – it's like asking a character in a painting why she always stares in the same direction.

The advantage of having no time is that you never need to worry about the order in which computations happen. If a variable is in scope then it also has the correct value, i.e. the value it has been assigned. (Which assignment may actually be “after” the computation in which it is needed – definitions can be reordered at will.)

Whereas in an imperative language – well, consider this program:

def numsum1(n):
sum = 0
i = 1
while i <= n:
sum = sum + i
i = i + 1
midterm = sum
while i >= 0:
sum = sum - i
i = i - 1
return (midterm, i)


If for some reason you need to refactor and pull the midterm definition behind the second loop, overlooking that it actually mutates sum again, then you would get the wrong result.

Now, you might well argue that this is defeated if you need to use recursion to basically fake mutation. Isn't there just as much, or even more, potential for mistakes if you have a recursive call using a parameter still called x that is effectively the same variable anyway?
– Not quite, because outside of the recursive calls the variable is guaranteed to stay the same. The refactoring problem with the above example wouldn't happen in a functional language.

Furthermore, as Odalrick already wrote, recursion isn't actually what's normally used to replace loops in functional languages. The idiomatic Haskell version of your program is

import Data.List (sum)

numsum :: Int -> Int
numsum n = sum [1..n]


...or, using more general-purpose tools,

numsum n = foldl' (+) 0 . take n \$ iterate (+1) 1


That's a bit of an exaggeration. Of course, you do sometimes need to take time into account even in a functional language. Obviously, if it runs somehow interactively (IO monad in Haskell), then those parts are subject to latency considerations. And even for completely pure computations, one side effect that you can't possibly avoid is memory consumption. And that's indeed the one thing that Haskell truely isn't good at: it's really easy to write code that typechecks, works, is correct, but takes gigabytes of memory (when a few kilobytes should have been enough) because some thunks are never garbage-collected.

• It's a bit easier to see if your example's loops are rewritten to recursive function calls with reassignment disallowed: you'll have the lines sum, i = numsumstep1(...); midterm = sum; sum2, i2 = numsumstep2(...). By not changing sum, midterm = sum means the same everywhere, and if you want it to hold sum2 instead, midterm = sum2 is a simple edit. Aug 16, 2021 at 19:07
• It's actually also easy to see this problem with mutable objects. If sum was a in-place mutable object instead and we never created new objects, sum and sum2 would point to the same object, so midterm = sum necessarily has a different value in different places, even if it technically is the same object. Obviously mutable objects have their perks, but this is definitely not a perk. Aug 16, 2021 at 19:09
• @BatWannaBe mutable variables, not mutable objects Aug 17, 2021 at 8:15
• Since the OP is using Python, note that the last Haskell example can be translated to def numsum(n): return functools.reduce(operator.add, range(n+1), 0). Aug 17, 2021 at 21:53
• And the second to last: def numsum(n): return sum(range(n+1)). Aug 17, 2021 at 23:00

I can only share my perspective. The way I think of it is that mainstream functional languages typically combine two themes: (1) support for higher-order functions, and (2) a preference for pure computation (referential transparency, no side effects, no mutation). In principle those two could potentially be separable, but they often go together in many mainstream functional languages.

Why is it considered beneficial to avoid mutation? Arguably, avoiding mutation makes it easier to reason about the correctness of code. This is especially so in the presence of concurrency, and also relevant when you have complex mutable data structures that are shared among multiple code modules. Variable reassignment is one form of mutation -- perhaps not the most dangerous, but if you set out to build a language that prefers pure computation, there is a certain conceptual clarity and cleanness in avoiding all mutation.

You can certainly have a function that is referentially transparent, yet that internally reassigns to local variables. However, verifying referential transparency can be more challenging in the presence of mutation. In contrast, if there is no mutation whatsoever, then it is becomes more trivial to verify that code is referentially transparent. So, there can be value to restrictions that are stricter than absolutely necessary, if they make it easier to verify correctness of code. We see this idea all over the place in programming languages, including in type systems (e.g., type systems: code that violates type-safety can potentially still be correct, but may be harder to verify is correct).

• I do see how it's cleaner if you do away with something that could cause problems. But it seems to me a compiler can easily recognize when only variables created inside the function are mutated. Just by allowing that, you can use loop structures that are equivalent to tail recursion. I have read that parallelism is cleaner without mutable state, but that doesn't seem applicable to the loop example where each iteration/function call depends on the last. Aug 16, 2021 at 4:45
• @BatWannaBe You could potentially have the compiler recognize some cases where a variable's scope is very small. But it would expand the semantics of the language significantly and for what benefit? It is already easy enough to program without local variables, and adding them would make a simple system (assignments are always static) into a more complicated system (assignments are mostly static except when the compiler says they don't have to be). Aug 16, 2021 at 11:35
• "But it seems to me a compiler can easily recognize when only variables created inside the function are mutated." The Koka programming language does this. Aug 16, 2021 at 12:36
• @Sriotchilism O'Zaic That's a good point, I HAVE been asking this question with the implication that loop reassignments are an easier or more convenient syntax to have. That's more subjective, of course, but then again people are generally skewed to this impression because imperative programming is more widely used. Aug 16, 2021 at 18:17
• @BatWannaBe Interestingly, imperative languages are also moving away from this paradigm - for loops being (mostly) replaced with iterators, using higher-order functions and composition, avoiding mutation... all of those make code much simpler to reason about. It's just another step on the road, like when we stopped using goto in favour of e.g. structured loops. Aug 18, 2021 at 6:42

If we want to be very precise with our words, we should say that in functional programming you don't assign a value to a variable, because assignment is a thing that you "do", and if you are telling the computer what to "do" then you are doing imperative programming instead of functional programming.

In a functional programming language, the code let x = 1 is not an instruction to assign the value 1 to the variable x; it is a declaration that the variable x is equal to 1. That is, the = symbol is used in its mathematical meaning to say that those two things are the same, interchangeable; not in its imperative programming meaning as an instruction "take the value 1 and store it in the memory location labelled x".

So, variables cannot be reassigned because they cannot be assigned in the first place. If you write let x = 1 and let x = 2 in a functional language, you are declaring that x is equal to 1 and equal to 2, which means you are declaring that 1 is equal to 2, because mathematical equality is transitive. It would not be useful for a language to allow you to declare that 1 is equal to 2.

• Some (older) languages use := for assignment, to distinguish it from = which means equality. Although we also need to distinguish a check for equality (usually written ==)! Aug 17, 2021 at 12:32
• I like the word « binding » here: in a functional lang, you create bindings. New bindings may shadow old ones, but that is separate from mutating the binding (like set! in lisps) or mutating the value in the binding (completely different). Aug 17, 2021 at 13:13
• @Warbo Indeed; there's also the symbol <- for assignment in some languages. I think it's a quirk of history that we use = to mean assignment in so many languages, when assignment and equality are such different concepts. Aug 17, 2021 at 15:13

There are several reasons, but they boil down to three main points:

• It's easier to reason about correctness, especially in the context of complex semantics (e.g. existential types, lazy evaluation) and security.
• It allows for optimisations that are not possible if data can change underneath.
• It allows for a transparent models of multi-threading, since read-only data does not need to be protected.

It's worth noting that non-functional languages do it too, and for much the same reasons. Java, for example, has an immutable String type. This allows static string data to be stored in read-only memory (e.g. on a microcontroller or smart card), and also makes for a more efficient and easy-to-prove security model when running potentially untrusted code.

You can't pass a String to a security-conscious part of the standard library such as the SecurityManager and then modify it after the event or in another thread. Nor can you use a String as a key in a binary search tree or hash table and then modify it, thus invalidating the data structure's guarantees.

• This seems more about immutable types and their instances. Java still lets you reassign a String variable to another String instance. Aug 16, 2021 at 9:30
• @BatWannaBe it's an analogous example, all of the same desirable properties of immutable values apply to bindings. Aug 16, 2021 at 17:58
• Oh I see, I can definitely remember weird and unpredictable stuff with reassignable variables in closures, that is basically the same as holding a mutable object as internal state. Like globals, this is another thing that's discouraged unless someone REALLY wants to faithfully represent a weird math function with internal state. Aug 16, 2021 at 18:24
• “It allows for optimisations that are not possible if data can change underneath” is the exact reason that the LLVM compiler infrastructure requires its “register” values to be in static single assignment form. Aug 17, 2021 at 21:59
• @NeilMeyer In-place data modification (which declarative programmers sometimes call "destructive update") is really what computers "do" at a low level. If you've ever programmed an algorithm which assigns a value to an element of an array, one of the fundamental "Fortran inner loop" operations, then you have changed data. It's "destructive" because the old version of the array is no longer available. Aug 18, 2021 at 23:49

In functional programming, great pains are taken to be able to know exactly what a computation depends on. The way in which you make variables be mutable, there can be cascading effects on the rest of the language.

If you just make them mutable, in that they are reference cells, then what you are effectively doing is wrapping the entire language in a state monad, where every variable in every closure becomes part of global state. For example, this is something that mutable variables let you do (in Python 3):

def make_counter():
val = 0
def count():
nonlocal val
val += 1
return val
return count

c = make_counter()
print(c()) # 1
print(c()) # 2
print(c()) # 3


That is not so good for analyzing the behavior of a program. Analysis is much easier if you can ignore the order in which expressions are evaluated.

It is easier to simply disallow mutable variables entirely than to develop a well-designed system that gives you useful, safe, and analyzable mutation.

One language that seems to have succeeded in this regard is Lean 4. It has a system that automatically inserts the correct folds into a monadic do-notation block to implement mutable variables. Here is an example translation of your program (using $$0 \leq i < n$$ rather than $$1 \leq i \leq n$$):

def numsum1 (n : Nat) : Nat := do
let mut sum : Nat := 0
for i in [0:n] do
sum := sum + 1
sum


This is using the "identity monad" and gets turned, effectively, into your numstep2. When it is compiled to C, it should even be a for loop with a mutable sum variable (though I didn't check).

Other monads, like the IO monad, also get local mutable variables through this system.

To be clear, the variable isn't "really" mutating since each iteration of the loop is essentially a new sum variable containing the updated value. However, the language doesn't have an interface where you can get a pointer to a mut variable, so you can't really say whether it is "really" updating in-place or not. And in fact, the runtime takes advantage of this with the Perceus functional-but-in-place paradigm.

• And unlike the OP's numstep1, the do block syntax syntax also makes clear what the scope of the mutable variable is. Aug 17, 2021 at 1:12
• +1 for Perceus ;) Aug 18, 2021 at 4:59

What would it be like to have variable reassignment in functional programming?

First i is 0, then you do something and change i to 1 ...

But that is "do this, then that". Imperative programming; not functional.

Functional programming is declarative. You write a whole bunch of functions and the computer takes care of calling them as needed. If you had i = 0 and then a bit later i = 1 in the same scope, the compiler could decide to set i to 1 first and then to 0.

Obviously no one wants a language to do that so it is simply disallowed.

So the answer is ultimately, because it is a functional language. If it allowed reassignment it would be an imperative language.

edit: I think what you are actually after is a more loopish way of functional coding.

While recursion is common and powerful, the loop equivalent in functional programming is genererally map or reduce.

It's a bit awkward in Pyhon but:

import itertools
import operator

def numsum3(n):
all_numbers = itertools.count(0)
n_and_forward = itertools.islice(sums, n + 1, None)
return next(n_and_forward)


Make a list of all the numbers. For all the numbers, sum the previous number and put it in an list. Discard all numbers up to the (n+1)th number (+1 because you used <= ). Return the first number in that list.

It is awkward in Python, but in functional languages this would be much easier to write.

"computer takes care of calling them as needed"

Exacly how this works depends on the language. Haskell uses monads; Elm has a "core" that does things outside the language; Erlang has a VM that does stuff.

This is one of the strengths of functional programming. The programmer actually cannot write very specific code so the "compiler" is free to do whatever it needs to.

• In addition, I think from a functional perspective a statement like "x = x + 1" doesn't even really make sense. "First x was 10, and now it's 11." But the whole principle of referential transparency is that x is 10. It can't then also be 11, that wouldn't be x anymore, but x + 1. Aug 16, 2021 at 15:57
• @JordiVermeulen Yeah, it doesn't make sense. But I didn't realise how little sense it makes until I started thinking about it, so: an interesting question. Aug 16, 2021 at 16:11
• @JordiVermeulen well, it can make sense if it's possible for x to be the same as x + 1. Of course that doesn't work out for number addition, but the general principle is that you're finding a fixpoint, and that can be quite useful, especially with lazy evaluation. Aug 16, 2021 at 17:32
• @leftaroundabout I believe that that is typically achieved through repeated function application, so something like fix f := f(fix f). Aug 17, 2021 at 10:57
• @JordiVermeulen yeah, but I Haskell you can also simply do stuff like x = "hi "++x. The result is an infinite string "hi hi hi hi h...". This can then either be trimmed to finite length (take 20 x), or used as input to some stream processor that just keeps going. Aug 17, 2021 at 11:29

Optimizers in C++ turn traditional C++ code into static single assignment when it can.

You can think of traditional imperative programming as chaining together functional steps.

struct state {
int sum;
int i;
};

auto numsum1 = [](int n){
return fpipe{} |
[]{ return state{0, 1}; }
| while_loop( [n](state s){ return s.i<=n; }
)(
[](state s){ return {s.sum+s.i, s.i+1}; }
)
| [](state s){ return s.sum; };
}


this is a purely functional version of the same imperative code with no recursion in "psudeo-code" that I could literally make compile in C++. [capture](arguments){body} is a C++-esque definition of a lambda, and | represents "piping the previous return value as an argument to the next function".

In this case, everything is immutable, nothing can be changed in any line of code above.

Converting traditional procedural code to this format makes reasoning about it by the compiler insanely easier, which in turn makes optimization easier.

The same is true for a human who gets used to it. Variables don't change their meaning or value in a given function call; they always have the same meaning.

This pattern "variables mean one thing", "data flows are explicit", "build algorithms out of smaller algorithms" is pretty fundamental to functional programming.

Disallowing assignment is part of the definition of "functional programming" and "functional language". On one level, you're simply asking why the definition of "functional language" is correctly being applied, so that languages which allow mutation of local variables are not eligible.

Why is variable mutation excluded from the definition of "functional"? Firstly, variable mutation will not achieve anything unless you have multiple execution code paths which can reach the same point. For instance:

let a = 0
if condition
a = 4
else
a = 5


but this doesn't exist in functional programming also. There are no statements. An if/then conditional in a functional language is an expression which calculates a value. In a functional language, the body of a function can consists of zero or more variable binding constructs, followed by an expression. Those binding constructs are not statements, though; they are just a way to factor out values from the body expression by giving them names, like in mathematics.

Since there are no statements in functional programming, variable assignments serve no purpose, because a variable assignment is a statement which alters a variable in order to induce a change in the calculation performed in other statements. And, not to mention, that since there are no statements and variable assignment is a kind of statement, it is ruled out that way.

A functional language can allow rebinding a variable in the same scope. For instance:

let x = 0
let x = x + 1


this is not assignment though; these are two different x variables, where the second one shadows the first one. A functional language would provide no way for the first let x = 0 to be skipped; e.g. this would not be featured in a functional language:

goto label
let x = 0
label:
let x = x + 1


To reiterate, the let bindings are not imperative statements. The notation:

let x = 0
let x = x + 1
x + x  # body expression


is just a verbose spelling of:

let x = 0 + 1
x + x


which is just another spelling of:

1 + 1


which is just another spelling of

2


"Functional" is all about functions: calculating by applying functions to values. In the purest form of functional programming, lambda calculus, there are no variables, other than function parameters.

The Lisp language (not functional, by the way, but supporting functional programming concepts) originally had no let operator at all for binding local variables. lambda came first, and let was invented as a syntactic sugar for a lambda. So that is to say if we have:

(let ((x 1)
(y 2)
(+ x y))


This can be written as a call to an anonymous function:

((lambda (x y) (+ x y)) 1 2)
^^^^^^^^^^^^^^^^^^^^^ ^^^
function            args


These two expressions notate exactly the same thing: binding x to 1, y to 2 and evaluating(+ x y) producing 3.

So when you think of a variable in the context of functional programming, you should think "function parameter". If you look hard enough, you will see the function.

When local variables are bound prior to the evaluation of some expression that references them, you can think of it as the parameters of an anonymous function receiving formal argument values.

In functional programming, every variable is a actually a formal parameter, and the only way it receives a value is by receiving a formal argument as part of a function call. And, so, that's the nutshell of why there is no assignment and why it's called "functional".

The answer is really purity. Pure functional languages strive to be pure functional languages. That involves not doing impure things.

I'm just learning F# right now. I notice that it has a policy of "variables are immutable by default, but can be declared to be mutable." So F# would be an example of a language that chose not to go the purist route.

Thanks to the Church-Turing Thesis, we know that you can convert between any lambda calculus problem and a corresponding Turing machine. This implies that there's always a way to go from functional programming constructs to imperative constructs, and back. We can always construct a pure functional program which is isomorphic to a functional program that has some mutable variables. Yakk's answer points at Single Static Assignment (SSA) which is one algorithm which helps tease apart assignments, shepherding it towards pure functional languages if one wishes.

Its all a matter of the intent of the language designer. Most of the big functional languages I know of were designed by people who wanted to explore pure functional languages and who believed that the notation of functional languages was superior to that of imperative languages. Their languages reflect these philosophies.

As a practical manner, as a language designer, consider the details that have to be handled when permitting something like re-assignment in a functional language. You have to make sure of two things:

• Reassignment of variables does not break assumptions that you relied on for the effectiveness of your language (referential transparency being the big one)
• Your users need to not be surprised by where reassignment works, where it doesn't work, and how it acts. Surprised users are unhappy users when it comes to programming languages.

Personal anecdote: I just dealt with the fun of the opposite of the question you ask -- the addition of functional bits into an imperative language. I just found out that C++'s std::function does not provide any guarantees regarding the use of dynamic memory, even in situations where it is clear that such dynamic memory could be avoided. It depends on the language implementer to decide when and where dynamic memory is needed.

Having now written a library using std::function in an environment where such dynamic memory is forbidden, I now need to go back through it and basically rewrite the entire API... Its quite exciting. You can hear the thrill in my voice as you read this, can't you? I am a user that got surprised.

### It’s closer to what an optimizing compiler does

Back in the olden days, on compilers that couldn’t optimize worth a DRAM, it was necessary to tell the compiler to throw out the old value we no longer needed, and replace it with an updated one. Early programming languages tried to stay close to the low-level operations of the processor, which would update a variable in a register or memory. But modern compilers perform dependency analysis, code movement and register allocation. They’re better at figuring out when they can drop or spill a variable from a register than a human is. So you can now declare every variable you need as a static single assignment, and let the compiler transform your high-level computation into efficient code.

Traditional functional languages transform code into continuation-passing style, moving blocks of code around so that the computations execute after their dependencies. They also allocate registers so that any quantity that’s no longer needed gets discarded, freeing up a register for another quantity that will be needed soon. They do this better than humans ever could: if you keep around a variable that you no longer need, you wast a register, and if you drop it too soon, you cause a bug the compiler can’t catch.

Unmodifiable variables are in many ways easier to optimize, since you’ll know for sure that you can do the computation once and re-use the value, you know for sure when it’s safe to use a reference instead of cloning the object, you know for sure on modern processors that reading the variable is thread-safe, and so on. Some computer scientists go further and try to prove that certain program transformations are provably correct on pure functions, in category theory.

Even many compilers for procedural languages transform code like x = x + 1 into a static single assignment, equivalent to x_1 = x + 1.=, and then treat x and x_1 as if they were different, immutable variables with a dependency between them. More complicated expressions, such as conditional assignments, get transformed into phi functions on the right-hand side. There’s an efficient algorithm to transform an abstract syntax tree in SSA form into one in CPS form and then apply all the optimizations from that.

If the optimizer is going to try to produce good code by transforming the program into a series of pure computations anyway, it’s less likely to get confused if the source code is written that way.

### It prevents certain bugs

In this pseudocode,

y = f(x)

if (a > b)
x = x + 1

z = g(x)


What is the value of x when z is computed? Are we sure that x always gets properly initialized? If this code gets refactored so z = g(x) gets moved right after y = f(x), which you might want to do for clarity, its meaning sometimes changes, giving you a Heisenbug. If you’re reviewing a large function with many possible paths of execution, when we see x being used, how was it set in this context?

In a functional language (or even a hybrid like Rust), you might write something like

let y = f(x0)
x1 = if   (a > b)
then x0 + 1
else x0
z = f(x1)


In many languages, you could even initialize z before x1, and there will be no doubt what you meant. Declaring x0 and x1 is completely unambiguous and the meaning of the same symbol does not change if you move it elsewhere in the same block. You can also be certain that x0 and x1 were initialized once and only once, and what they were initialized to.

### It’s easier to analyze

It isn’t, in general, possible to deduce whether a code path in an arbitrary program is reachable. However, if you restrict the language so that only certain safe operations are possible, you can more safely prove what will and won’t happen. For example, when variables are immutable, many complex special cases involving modification through an alias cannot occur. C++ even introduced a special form of immutability, constexpr, specifically to make it possible for the compiler to perform calculations on constants at compile time and fold them into the executable.

Or, let’s take the great example you gave:

def numsum1(n):
sum = 0
i = 1
while i <= n:
sum = sum + i
i = i + 1
return sum


We want an optimizing compiler to be able to tell that this is all equivalent to return n. Optimizers for imperative languages are heavily-focused on analyzing loops, and this while loop is simple enough that I’d expect a modern C, C++, Java or Rust compiler to be able to figure the translation out.

### Functional languages have equivalents

A functional language can also have variables that mutate within each iteration of a loop, only it would refactor into a tail-recursive function:

numsum1 n = go 1 0 where
go (n+1) sum  = sum
go i sum = go (i+1) (sum+1)


Or, if we’re not worried about negative numbers as inputs (although we could easily handle those too):

numsum1 n = go 0 n where
go sum 0 = sum
go sum i = go (sum+1) (i-1)


Tail recursion on a pattern match like this is exactly equivalent to the loop: you perform a test at the beginning of each repetition to see whether you continue, and if so, increment the loop counter (which on a modern ABI means updating registers and re-using the same stack frame) and jump back to the start of the loop/tail-recursive function. Both versions have a local variable named i within the block of code whose value changes every time it runs. Since imperative-language compilers also want to be able to optimize tail-recursive functions, it’s simpler for the compiler to be able to rely on a great optimizer for recursive code, and not need to analyze arbitrary while loops too.

numsum1 can be mechanically translated into numsum2. In fact, the translation is essentially the same as the one performed anyway by virtually all optimizing compilers, as Andrew Appel pointed out in the paper SSA is Functional Programming. *

Since it can be done automatically, you could argue that there's no reason to make the human programmer do it.

I think the strongest argument against this is that there's nothing stopping you from writing your entire program as one big function. Then you can mutate global variables, since they are local to the current function. The automatic translation to SSA/functional form will convert the globals to hidden parameters, so everything will work. But the larger the program gets, the more those parameters will truly be hidden from the human programmer, which is the problem that pure functional programming is meant to avoid.

If limited to small functions like your example, where the usage patterns are obvious, I think the automatic translation would be harmless, but also not very useful since it's easy to transform by hand. When it's difficult to do the transformation by hand, it's because it's hard to analyze all of the dependencies in the code, and that's when you should do it by hand, since functional programming is about making those dependencies explicit (and ideally minimizing them).

* I'd say rather "SSA is a hacky subset of functional programming", since the functional form includes the SSA flowgraph, the dominance tree, and additional information not found in either of them in a nice unified way, and I think it's easier to understand.