So here, concretely, is what I'm contemplating: 1. Strings will have unspecified internal representation, but well-formed strings will contain code points, *not* code units. 2. There will be some form of string accessor object or set of functions. The general idea is that you specify the index of the first desired code point and the length, and get back a StringAccessor containing those code points. 3. The string accessor notion can be extended to other things such as code units.
The question then becomes: why shouldn't we simply decide that vectors make perfectly fine holders of code units, and Strings are the means for representing code points? The only objection I can think of is that this is not (regrettably) how various native string representations operate (e.g. .Net). shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
