On Thursday, 6 September 2018 at 07:23:57 UTC, Chris wrote:
Seriously, people need to get over the fantasy that they can
just use Unicode without understanding how Unicode works.
Most of the time, you can get the illusion that it's working,
but actually 99% of the time the code is actually wrong and
will do the wrong thing when given an unexpected (but still
valid) Unicode string.
Is it asking too much to ask for `string` (not `dstring` or
`wstring`) to behave as most people would expect it to behave
in 2018 - and not like Python 2 from days of yore?
I agree with Chris.
The boat is sailed, so D2 should just go full throttle with the
original design and auto decode to graphemes, regardless of the
performance.
