Notes

- A returned [ndarray][@stdlib/ndarray/ctor] function interface has the following signature:

`text
f( x, y, ... )
`

where

- x: [ndarray][@stdlib/ndarray/ctor].
- y: [ndarray][@stdlib/ndarray/ctor].
- ...: additional [ndarrays][@stdlib/ndarray/ctor].

- The number of [ndarray][@stdlib/ndarray/ctor] function interface parameters is derived from nargs, the number of input [ndarrays][@stdlib/ndarray/ctor] is derived from nin, and the number of output [ndarrays][@stdlib/ndarray/ctor] is derived from nout.

- An [ndarray][@stdlib/ndarray/ctor] function (i.e., a value provided for the fcns argument) should have the following signature:

`text
f( arrays[, data] )
`

where

- arrays: array containing input and output [ndarrays][@stdlib/ndarray/ctor].
- data: [ndarray][@stdlib/ndarray/ctor] function data (e.g., a callback).

- For convenience, a single [ndarray][@stdlib/ndarray/ctor] function may be provided which will be invoked whenever the [ndarray][@stdlib/ndarray/ctor] argument data types match a sequence of types in types. Providing a single [ndarray][@stdlib/ndarray/ctor] function is particularly convenient for the case where, regardless of array data types, traversing arrays remains the same, but the [ndarray][@stdlib/ndarray/ctor] function data differs (e.g., callbacks which differ based on the array data types). For example, the following

`javascript
var unary = require( '@stdlib/ndarray-base-unary-by' );

function foo( x ) {
return x * 10.0;
}

function bar( x ) {
return x * 5.0;
}

var fcns = [
unary,
unary
];
var types = [
'float64', 'float64',
'float32', 'float32'
];
var data = [
foo,
bar
];

var fcn = dispatchBy( fcns, types, data, 2, 1, 1 );
`

is equivalent to

`javascript
var unary = require( '@stdlib/ndarray-base-unary-by' );

function foo( x ) {
return x * 10.0;
}

function bar( x ) {
return x * 5.0;
}

var types = [
'float64', 'float64',
'float32', 'float32'
];
var data = [
foo,
bar
];

var fcn = dispatchBy( unary, types, data, 2, 1, 1 );
`