Major performance problem with std.array.front()

[ponce]

On Monday, 10 March 2014 at 11:04:43 UTC, Nick Sabalausky wrote:
>
> I may have missed it, but I don't see where it says anything 
> about validation or immediate sanitation of invalid sequences. 
> It's mostly "UTF-16 sucks and so does Windows" (not that I'm 
> necessarily disagreeing with it). (ot: Kinda wish they hadn't 
> used such a hard to read font...)

I should have highlighted it, their recommendations for proper 
encoding handling on Windows are in section 5 ("How to do text on 
Windows").

One of them is "std::strings and char*, anywhere in the program, 
are considered UTF-8 (if not said otherwise)."

I finds it interesting that D tends to enforce this lesson 
learned with mixed-encodings codebases.