std.uni vs std.unicode and beyond?

[Idan Arye]

On Tuesday, 21 May 2013 at 18:23:42 UTC, Dmitry Olshansky wrote:
> 21-May-2013 22:12, 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.
>
> I see people have no idea what Unicode is about.
> Unicode is not only the encoding - it's a de facto standard of 
> internationalization and related algorithms. UTF is encoding.

If I see a module called "utf" and I don't see a module called 
"unicode", I automatically assume that "utf" contains Unicode 
related stuff as well. And visa versa - if I see "unicode" and 
not "utf", I assume "unicode" contains the UTF stuff.

Sure, they are not the same - but they are related enough that 
people will expect them to share a module.