Example Of Not A Function

How to Identify When a Relationship Isn't a Function

Common Example Of Not A Function Situations

A function requires that every input maps to exactly one output. When it doesn't, you're looking at something that isn't a function. The most straightforward way to see this is with the vertical line test on a graph. If any vertical line crosses the curve more than once, you've found an x-value that corresponds to multiple y-values, which disqualifies it. Take the equation x = y². If you plug in x = 4, you get y = 2 and y = -2. Two outputs for one input. That's not a function. The graph is a parabola opening to the right, and a vertical line at x = 4 intersects it in two places. This is probably the cleanest example of not a function you'll run into on any math test or exam. Here's the practical side of things. I was grading a set of student responses last semester where nearly everyone correctly identified piecewise definitions and absolute value graphs as functions, but they kept missing relations where a single x-value clearly produced two different outputs. The problem was usually visual processing, not conceptual understanding. They'd see a curve and assume it was fine without checking whether any vertical line hit it twice.

The workaround I ended up using was having students trace each graph with a ruler held vertically, moving it left to right across the domain. If the ruler ever touched the graph at more than one point at any position, they flagged it. It took about twenty minutes during one class period and fixed the issue for everyone who tried it.

More Examples Of Not A Function

Beyond x = y², there are several other common cases. The circle equation x² + y² = r² fails the function test for any r greater than zero because every x-value between -r and r has two corresponding y-values. The top half and bottom half of the circle give positive and negative square roots respectively, and a function can't do that. Vertical lines themselves are another example. x = 5 means every possible y-value is paired with the single x-value of 5. Infinite outputs for one input. Definitely not a function, and it trips people up because it's such a simple equation. Inverse trigonometric functions reveal an important subtlety. The full inverse sine relation, written without restrictions, is not a function because sin(/6) and sin(5/6) both equal 1/2. The standard workaround is restricting the domain of sine to [-/2, /2] so that arcsin becomes a proper function. If you're working with inverse relations and don't apply this restriction, your results will be wrong every time.

I ran into this exact issue when I was helping someone set up a signal processing model. They needed the inverse sine of a ratio and just used the raw calculator output without considering the periodicity. The model gave them phase angles that were off by in roughly half their cases. They were puzzled for about three days before we caught it. Restricting to the principal value branch fixed it immediately.

How to Test Any Relation Systematically

Start by isolating y if you can. When y appears to a single power and there's no ambiguity, you usually have a function. When y appears squared or under a radical with both positive and negative branches, check whether different y-values share the same x. For tables of values, look for repeated x-values paired with different y-values. That's an immediate fail. For mapping diagrams, any input arrow branching to more than one output means the relation isn't a function. When dealing with parametric equations like x = t² and y = sin(t), the analysis is less obvious. Here you need to eliminate the parameter or check whether two different t-values produce the same x but different y-values. In this specific case, t = 1 and t = -1 both give x = 1 but y = sin(1) and y = sin(-1), which are different. So this parametric relation is not a function of x, though it is a valid parametric curve.

This distinction matters in applied work. If you're building a controller and your sensor reading maps to multiple possible system states, you don't have a function and your control logic will break. I've seen this happen in robotics when encoder feedback was interpreted as a direct position function instead of being recognized as an ambiguous angular measure. The robot would randomly choose between two positions for the same encoder value and behave erratically.

Why This Distinction Matters in Practice

People often treat the function/non-function distinction as purely academic. It isn't. Every differential equation solver, every numerical integration routine, every optimization algorithm assumes you're working with a function. Feed it a relation that isn't one and the results are either garbage or the program crashes. Implicit differentiation is a good example. When you differentiate an equation like x² + y² = 25, you're temporarily treating y as a function of x even though the full relation isn't a function. The trick is that you're working on a branch where it is a function locally. If you don't respect that boundary, your derivative calculations become invalid at points where the implicit function theorem breaks down, specifically where the partial derivative with respect to y equals zero. The circle example again: at the points (5, 0) and (-5, 0), the tangent is vertical and dy/dx is undefined. You can still do implicit differentiation through those points algebraically, but the result tells you the slope is infinite, which means the function framework has hit its limit. That's useful information in itself. It tells you where your model needs to switch from y = f(x) to x = g(y) or use parametric form instead.

A Counter-Intuitive Point Most People Miss

A relation can fail to be a function globally but still be a function on restricted domains. x = y² fails everywhere you'd normally graph it, but if you restrict y to be non-negative, you get y = x, which is a perfectly valid function. Similarly, if you restrict y to be non-positive, you get y = -x, also a function. This restriction approach is standard in higher mathematics but gets glossed over in introductory courses. Students learn the vertical line test and move on without understanding that many "non-functions" are actually functions waiting for a domain restriction. This matters when you're composing functions or finding inverses, because composition requires both the outer and inner expressions to be functions on their respective domains. I encountered a situation once where someone was trying to compose two inverse relations and got stuck because neither was a function on its natural domain. Once we identified the correct principal branches for both and composed on the intersection of those restricted domains, the whole problem became solvable. It saved probably six hours of trying to force the unrestricted versions to work.

Bottom Line

The core rule is simple: one input, one output. Everything else is just applying that rule to different representations. Tables, graphs, equations, parametric forms, mapping diagrams — they all follow the same constraint. When you find a case where a single input produces multiple outputs, you've found your example of not a function and you know exactly what to do about it.