Everything is the Same, Everything is Different
When 2+2 is not 4
In this post, I’ll argue the merits of a functional programming language where the equality operator respects the principle of functional equality.
This principles states that, if
b are equal, then there should exist no function
f for which
f(a) != f(b).
Many, if not most, FP languages violate this principle.
Same Length, Different Measurement
The international inch is defined as precisely 2.54 centimeters. So 2.54cm = 1in.
Suppose we have a Measurement class in some OO language, with a constructor that takes a magnitude and a unit, like so:
length1 = measurement(2.54, "cm")
length2 = measurement(1, "in")
length1 == length2?
You could say that they are equal by the very definition of international centimeters.
toString(length1) is “2.54 cm”, and
toString(length2) is “1 in”. This means
toString(length2), and therefore
length2 are different. So then how can they be equal?
What do You Mean by “Equal?”
My answer is that
length2 are the same, and they are also different.
They are the same in that they represent the same physical distance. But they are different in that they are expressed in different units.
Does 2+2 = 4?
The answer to this quintessentially trivial question really depends on what do you mean by equal!?
Let’s say I define
b in a Haskell program like so:
let a = 2+2
let b = 4.0
b? If the question is whether they are equal points on the number line, then the answer is yes. But in other ways,
2+2 obviously is not the same as
4.0. They even look different. One expression has a little
+ in it, the other has a decimal point. One is an int, the other is a float.
But do these differences matter?
I propose that, when defining equality, what matters to programmers is whether two values are interchangeable. If
a is really equal to
b, you should be able to replace
b anywhere in your code and nothing in your output would change at all. In other words, this statement should never be true:
(a == b) && (f(a) != f(b))
This concept is related to the FP concept of referential transparency: an expression is referentially transparent if it can be replaced with its value without changing the behavior of the program.
But shouldn’t we also expect that any value can be replaced with an equal value without changing the behavior of the program?
For an FP language to really respect the spirit of referential transparency, it should respect functional equality.
It’s Easy to Get Equality Wrong
The strict requirements of functional equality can be easily broken. In the Haskell case, this expression is true:
(a == b) && (show(a) != show(b))
show(a) will be “4”, and
show(b) will be “4.0”. So the two values are not functionally equal.
Violating Functional Equality Creates Problems
The user of your class my assume that two objects that are equal behave in the same way and are therefore totally interchangeable, when they are in fact not.
Suppose a developer writes a program that plots data on charts, placing labels with the numeric value next to each point.
She may be encounter a situation where the same chart sometimes includes a decimal point in the labels, and sometimes doesn’t. She is perplexed when she discovers that equal inputs produce different outputs, which her intuition says should not be possible in a functional programming lgnguage. Only after spending considerable time debugging does she realize that the inputs, while passing the
== test, are actually different, because one contains floats and the other contains integers. She’ll then realize that she needs to rethink her definition of “equality”.
Equality Across Types
2+2 == 4.0 should evaluate to false?
That would be a problem as well. It would certainly be non-intuitive for many programmers, and could easily lead to very frustrating debugging sessions.
But I would say that, if you want a language where ints and floats act differently, then they should not even be comparable. The programmer should be required to explicitly convert them into a common type before comparing. The expression
2+2 == 4.0 should produce a compile-time error. You should be required to write something like
(float) 2+2 == 4.0, making it very clear what you mean by “equal”.
I would also argue that different types for ints and floats may not be necessary in modern languages — and indeed most dynamic languages these days make no distinction.
The functional equality principle allows
b to pass the equality test only if it is never true that
f(a) != f(b) for any f.
With a language that enforces functional equality, programmers will still sometimes fail to really think through what they mean by “equality”, and be surprised when two values they expect to be equal are not. But I think this is okay — it will force programers to more concretely understand and define what exactly they mean by equality, and to write more clear and correct code.