std.uni vs std.unicode and beyond?

[Regan Heath]

On Tue, 21 May 2013 19:23:36 +0100, Dmitry Olshansky  
<dmitry.olsh at gmail.com> 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.

So.. surely this suggests some structure would help with that, i.e.

std.encoding.ascii
std.encoding.latin1
std.encoding.utf

std.i18n.unicode

R

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/