> Yes lists are more prevalent in Scheme code. But vectors allow us to
> reference an item that is beyond car and cadr. Also, how would you
> represent vectors and pairs?

Note that I've specifically said lists (as in, a proper list terminated
with the empty list, allowing it to be traversed fully using for-each
and alike), not pairs. Handling constructs such as alists is out of
scope.

I've thought about supporting vectors using a similar construction to
the nested code, but given how little they are used it doesn't seem
worth the effort to prove that construction to be correct.

Vasilij