Re: `aset` on strings, changing the size in bytes

[Helmut Eller]

On Fri, Sep 07 2018, Stefan Monnier wrote:

> Currently, this indirection comes "for free" since we use that same
> indirection to let the GC compact the set of string-data-bytes objects
> to try and reduce memory fragmentation.  But I think we should not have
> our high-level API impose such an indirection at the lower level,
> especially since this (mis)feature is virtually never used.

Would it be hard to have two internal string types, where the "normal"
string type has no indirection but can be changed (by updating the type
header) to the other type that has the indirection?

Helmut