On 2012-08-02 08:39, Walter Bright wrote:
That's what I've been saying. So why have an input range of dchars,
which must be decoded in advance, otherwise it wouldn't be a range of
dchars?
Your first requirement is a bit strange and confusing:
"1. It should accept as input an input range of UTF8."
To my understand ranges in Phobos are designed to operate on dchars, not
chars, regardless of the original input type. So if you can create a
range that operates on UTF8 I don't know if that will be usable with the
rest of the Phobos functions expecting ranges of dchars. Basically
making this type of range useless since it cannot use any other
functionality in Phobos.
The current state of Phobos: you either have a range of dchars or you
don't have a range, you have an array or something else.
--
/Jacob Carlborg
