>
>
>
> There may be a more general motivation for efficient string concatenation
> and subdivision, but the argument for that is highly situational.
>

Yes likely parsing XML /HTML will be a big use but situational.

>
> The main question, I think, is whether we are willing to trade linear
> access time for substring reuse. My personal sense is that we probably
> should *not* do this with the primitive string type, but we should
> perhaps consider introducing a SlicedString type and a Stringish type class.
>

Concur , intuitively. A new class doesn't loose you much so long as its
situational and not common . In the case of the above your working on large
amounts of data  so a special type would incur negligible cost and be more
flexible.

Regards,

Ben
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to