Vectors
~~~~~~~

The `(scheme vector)` library now
provides a set of procedures that may supersede some
of the procedures described below.

[WARNING]
================================================================
The `(scheme vector)` library has almost nothing to do with the
13 libraries whose names are of the form `(scheme vector @)`,
where `@` is one of
`base`, `u8`, `s8`, `u16`, `s16`, `u32`, `s32`, `u64`, `s64`,
`f32`, `f64`, `c64`, or `c128`.
Those libraries provide support for homogeneous numeric vectors,
which are more space-efficient than using Scheme's more general
vector type to represent a sequence of numbers that all have the
same bit-level representation.
================================================================

If one of Larceny's procedures duplicates the semantics of
an R7RS procedure whose name is different, then Larceny's
name is deprecated.

proc:vector-copy[args="vector",result="vector"]

Returns a shallow copy of its argument. 

_Operations on vector-like structures_

proctempl:vector-like?[args="object",result="boolean"]
proctempl:vector-like-length[args="vector-like",result="fixnum"]
proctempl:vector-like-ref[args="vector-like k",result="object"]
proctempl:vector-like-set![args="vector-like k object",result="unspecified"]

A vector-like structure is a low-level representation
for indexed arrays of Scheme objects.  Vector-like
structures are used to represent types such as vectors,
records, symbols, and ports.

There is no way to construct a "generic" vector-like structure;
use the constructors for specific data types.

The vector-like operations operate on all vector-like structures.
All are integrable.
All are deprecated because they
violate abstraction barriers and make your code
representation-dependent; they are useful mainly to
Larceny developers, who might otherwise be tempted to
write some low-level operations in C or assembly language.
