it's broken and nobody seems to have noticed. that might be because the
interpreter doesn't care whether something is a list or a tuple.
if this is reintroduced for some reason, it should be done directly in
the affected code path.