Thanks Peter McGoron for working on SRFI 288: Compound Conditions. It
was in my opinion missing from R7RS. As far as I can tell, it is good
treatment of the topic.

1. (make-condition-type symbol fields) accepts as fields either a list
or vector. I don't remember whether vector as self-evaluating or not in
R7RS. In any case, it is unclear whether it is necessary to accept both
list and vectors. In other words, what does that freedom gives to users?

2. Anyway, whether fields are passed as vector or list, the returned
accessors are returned as a vector, which slightly more verbose and
cognitively heavy compared to a list, in particular when destructuring
the fourth returned value with `match`.

Why not choose lists for both argument and co-argument.

ref: https://srfi.schemers.org/srfi-288/