# Undo

Oh no, you've deleted a function after spending half an hour writing it! Well… hopefully your editor can help with that. But maybe you'll be interested to hear that BQN can reverse the action of some functions—ones that don't lose information. This capability is also used by Repeat () to repeat a negative number of times, and Under () in some cases.

↗️
2  "abcde"
"cdeab"

2  2  "abcde"
"abcde"

Above is one example of Undo () in action. Rotate shifts the elements of a list left, and undoing shifts them to the right. BQN's ability to undo functions covers a lot of cases and can seem somewhat magical:

↗️
(Fn  -1(¯1)) "BQN"
"BQM"

Fn Fn "BQN"
"BQN"

Here it undoes a function to decrement the last character by incrementing that character. In part this is enabled by the clean design of BQN primitives, because better-behaved functions like those using structural Under are easier to invert.

## The rules

If 𝔽 can be inverted exactly, then Undo just does that (or tries). However, there are also some other functions that BQN inverts. For example, the squaring function ×˜ has both a positive and a negative inverse, and yet:

↗️
×˜ ¯3
9
×˜⁼ ×˜ ¯3  # It's not the same!
3

Don't worry, this isn't 'nam. Undo doesn't always satisfy 𝕩 𝔽 𝔽 𝕩, but it does obey 𝕩 𝔽 𝔽 𝕩. That is, it gives one possible argument that could have been passed to 𝔽, just not necessarily the one that actually was. BQN is conservative in how it uses this freedom, so that it won't for example make up new elements entirely to find an inverse: 1 is one function that it could undo but won't. It's usually used when there's an obvious or standard way to pick which of the possible values should be returned.

In a BQN with floating-point numbers, computations are approximate, so the inverse is allowed to be approximate as well (any error should still be very small though).

↗️
6 - 6
8.881784197001252e¯16

## What's supported?

For the full list, see the specification. An individual implementation might support a lot more functionality than is required, so if you're not concerned about portability just try out whatever function you're interested in.

Arithmetic and simple combinators are usually invertible. A compound function that refers to its argument just once, like 6+⌽, can typically be undone, but one that uses the argument in two different ways, such as ⊢+⋆, probably can't.

A few notable inverses are the logarithm , un-Transpose , and Indices inverse /. Enclose inverse, <, is an alternative to First that requires its argument to be a unit array.

Structural functions like Take and shifts that remove elements from 𝕩 can't be inverted, because given the result there's no way to know what the elements should be. However, there are two special cases that have inverses defined despite losing data: these are and k where k is a constant (a data type, or k˙). For these, 𝕩 is required to match the always returned value 𝕨 or k, and this value is also used for the result—even though any result would be valid, as these functions ignore 𝕩.

↗️
3  4
Error: ⁼: Inverse does not exist

3  3
3

Of course BQN will never be able to invert all the functions you could write (if it could you could earn a lot of bitcoins, among other feats). But it does recognize some header forms that you can use to specify the inverse of a block function. BQN will trust you and won't verify the results your specified inverse gives.

{
𝕊𝕩:  𝕩÷1+𝕩 ;
𝕊𝕩: 𝕩÷1-𝕩
}

The above function could also be defined with the automatically invertible 1+÷, but maybe there's a numerical reason to use the definition above. Like a normal header, an undo header reflects the normal use, but it includes and possibly ˜ addition to the function and arguments. Any header that includes a function can have these modifiers added—even a fancy modifier header like 𝔽_m1⁼ab: or plain label like 𝕊:. The three forms are 𝕊𝕩:, 𝕨𝕊𝕩:, and 𝕨𝕊˜⁼𝕩:, and the two dyadic forms are also used to derive kF𝕩 and Fk𝕩 with a constant k.

↗️
G  { 𝕊˜⁼:𝕩-2×𝕨 ; 𝕨+2×𝕩 }
G2 7
3