std.uni vs std.unicode and beyond?

[Brad Anderson]

On Tuesday, 21 May 2013 at 17:53:02 UTC, Idan Arye wrote:

> The problem is that people that need Unicode stuff see 
> `std.utf` and assume that all Unicode related stuff are there.

I see (and experience myself) a lot of confusion over this.  
Dealing with strings a person constantly has to guess which of 
these modules has what they are looking for:

std.algorithm
std.ascii
std.conv
std.encoding
std.range
std.string
std.format
std.uni
std.utf

It's a mess. At least grouping the encoding stuff together would 
give it some structure.