Top 5

[Benji Smith]

Andrei Alexandrescu wrote:
> In addition, the std.encoding module (where's Janice? sigh) is very 
> promising in that it offers open-ended support to other current and 
> possibly future encodings. I plan to work on that at some time to make 
> it fast, because its use of delegates is inefficient. The advent of 
> ranges also clarifies that the right way to treat a string of any 
> encoding as a collection of characters is a bidirectional range: you can 
> move forward or backward, but there's no random access. Once a library 
> type UTFRange is in place, that will work with all current and future 
> algorithms accepting bidirectional ranges. Insertion and replacement in 
> strings is not easy to code, but certainly doable and most of the time 
> as efficient as for regular arrays.

Yeah, I'm really looking forward to trying out the UTFRange stuff when 
it becomes available. Nice work on that.

--benji