07-Mar-2014 06:37, Walter Bright пишет:
In "Lots of low hanging fruit in Phobos" the issue came up about the
automatic encoding and decoding of char ranges.

Throughout D's history, there are regular and repeated proposals to
redesign D's view of char[] to pretend it is not UTF-8, but UTF-32. I.e.
so D will automatically generate code to decode and encode on every
attempt to index char[].

...

Is there any hope of fixing this?

Where have you been when it was introduced? :)


--
Dmitry Olshansky

Reply via email to