Empty array

In the APL array model, an empty array is one with a bound of zero, that is, an array with no elements. While a nested list model has only one empty list, APL has many different empty arrays. These arrays are distinguished by their shape and prototype.

Examples of empty arrays are the empty numeric array Zilde and the empty character array. These arrays have different prototypes, and do not match in most APLs.

Empty array shape
The shape of an empty array is usually determined by shape arithmetic in the function which produces it. Because in most primitive functions the result shape is determined by the argument shapes and sometimes the numeric values of elements from the arguments (for instance, in the left argument of Reshape), the shape of an empty array is rarely in doubt.

The primary exception is when using the Rank operator on an array with no cells of the specified rank. Because the shape of each result cell might be determined by values in an argument cell, the appropriate shape may be impossible to determine.

The example above shows how an arithmetic rule can fail when using Rank with an empty array. For any positive integer, it's clear that   because each result cell is the array. However, the empty array  is indistinguishable from any other empty numeric array because it has shape   and prototype. This means Rank cannot determine the appropriate result shape. The Rank operator still attempts to find a sensible result shape: it executes the operand on a prototype cell obtained by reshaping the argument to the argument cell shape (here, the prototype cell is a scalar ), and uses the resulting shape to determine the shape of its final result. In this case, this succeeds in finding the appropriate result rank but not the desired shape.

If Rank is implemented by splitting the argument(s) into cells, applying the operand with Each, and mixing, then the above problem actually becomes an issue of empty array prototypes: the result of Split is empty, and calling Each on an empty array uses prototypes to determine prototypes, an unreliable operation.

Empty array prototype
Because an empty array has no elements from which a prototype could be derived, prototype or type information must be stored with the array.

Determining the prototype of an empty array when it is produced is often difficult, and may break identities even for simple functions. An empty array's prototype is far less reliable than its shape.

Consider the following identities for Catenate on vectors, one of which is empty. These identities always hold when  and   are non-empty, because the result is non-empty and its elements are entirely determined by the non-empty argument. However, if we consider the catenation then the first identity tells us that the result should be  while the second gives a result of. These two arrays do not match, so one of the identities must be wrong! In fact, the choice of which prototype to use for the result is a source of incompatibility among APLs. In Dyalog APL it has even been changed in the past. At one point the right argument's prototype was used; now we can inspect the first element of  to see that the left argument's prototype is used.

Reduction over a length-0 axis
If a reduction (using one of,  ,  , or  ) is performed over an axis of length 0, the resulting array is filled with identity elements. For example, the sum of an empty list is  because the identity element for addition is  : The identity element for a specific reduction always depends on the operand, and may depend on the argument array prototype. Dialects differ in their support for such reductions. All define identity elements for most scalar primitives, and some stop there (e.g. SAX), while others (e.g. Dyalog APL and APL2) define identity elements for various mixed functions.