Didn't realize this until finalization... While the generic names like
"xxxxxx@vector" to cover "make-s8vector", "make-u8vector",
"make-s16vector" are convenient, they will make it harder to
auto-extract procedure definitions from SRFI text once we get that
machinery going.

Perhaps the extractor program could be given SRFI-specific substrings to
expand. For SRFI 160 it could be:

(expand @vector
         s8vector
         u8vector
         s16vector
         u16vector
         s32vector
         u32vector
         s64vector
         u64vector
         f32vector
         f64vector
         c64vector
         c128vector)