make-uniform-vector bit vector versus array-set!

[Kevin Ryde]

In 1.8 there seems to be something a bit evil in array-set! on a bit
vector created by make-uniform-vector,

        guile> (define a (make-uniform-vector 15 #t #t))
        guile> a
        #*111111111111111
        guile> (array-set! a #f 0)
        guile> a
        (2207 . #<smob 80ba960>)

I don't understand all that stuff, but I got some joy from this
change.  Can someone (Marius?) confirm or deny?

        * unif.c (bitvector_set): Should be h->writable_elements not
        h->elements, the latter results in a segv in array-set! on a bit
        vector.

unif.c.writable_elements.diff
Description: Text document