Proposal for fixing dchar ranges

[Chris Williams]

On Tuesday, 11 March 2014 at 14:16:31 UTC, Steven Schveighoffer 
wrote:
> But I would never expect any kind of indexing or slicing to use 
> "number of code points", which clearly requires O(n) decoding 
> to determine it's position. That would be disastrous.

If the indexes put into the slice aren't by code-point, but 
people need to use proper helper functions to convert a 
code-point into an index, then we're basically back to where we 
are today.