A mess with GOOPS

[Panicz Maciej Godek]

Hi,
I've been using GOOPS with vectors now, and I've observed an annoying
feature. While "array-map!" et al. accept vectors, uvecs and arrays,
and so it is easy to write joint code for these types, this fact is
not reflected in the world of objects.
In other words, classes <vector>, <uvec> and <array> have nothing in
common, which requires me to triple the number of methods that could
accept any of these types.
If I would write any wrapping class hierarchy to embrace these
similarities, I would loose the advantage of having the special reader
extension for vectors and arrays, so I believe that this can be only
changed in the core of GOOPS.
Is there any possibility to do so?
Regards,
M.