[m-rev.] for review: mercury implementation of string.m

[Michael Day]

> This wouldn't be a problem for the C back-end, if one were to restrict
> update operations to unique strings.  However, the IL back-end does not,
> I believe, support mutable strings; instead one is expected to use the
> StringBuilder class, from which one can obtain ordinary strings.

Does this mean set_char and so forth cannot be implemented for the IL
back-end?

Seems like a good time to change the usage of strings in Mercury
generally, introducing a type for building strings, a type for breaking up
strings, and getting rid of the update operations on string itself (as
well as first_char).

Michael

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------