> A possible implementation-specific approach would be to treat > `make-vector` without a fill argument as turning on a bit which says > "Don't allow `vector-ref` (vel sim.) on this vector, and don't follow > its elements for GC purposes." Then the obvious vector-insert algorithm > would Just Work, provided there is some way of clearing the bit when > the programmer knows that every element has been set.
If I understand correctly, when the first element is assigned to the new vector, surely the implementation would have to clear the bit and initialise the other elements? I don’t doubt there are ways to optimise this, but I don’t think a naive implementation of this helps. Regards, Alan _______________________________________________ Scheme-reports mailing list Scheme-reports@scheme-reports.org http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
