On 5/31/16 2:21 PM, Jonathan M Davis via Digitalmars-d wrote:
I think that the first step is getting Phobos to work with all ranges of
character types - be they char, wchar, dchar, or graphemes. Then the
algorithms themselves will work whether we have auto-decoding or not. With
that done, we can
On Monday, May 30, 2016 14:24:23 Andrei Alexandrescu via Digitalmars-d wrote:
> On 05/30/2016 12:34 PM, Jack Stouffer wrote:
> > On Monday, 30 May 2016 at 16:25:20 UTC, Nick Sabalausky wrote:
> >> D1 -> D2 was a vastly more disruptive change than getting rid of
> >> auto-decoding would be.
> >
> >
On 05/30/2016 03:00 PM, Jack Stouffer wrote:
On Monday, 30 May 2016 at 18:24:23 UTC, Andrei Alexandrescu wrote:
That kind of makes this thread less productive than "How to improve
autodecoding?" -- Andrei
Please don't misunderstand, I'm for fixing string behavior.
Surely the
On Monday, 30 May 2016 at 18:24:23 UTC, Andrei Alexandrescu wrote:
That kind of makes this thread less productive than "How to
improve autodecoding?" -- Andrei
Please don't misunderstand, I'm for fixing string behavior. But,
let's not pretend that this wouldn't be one of the (if not the)
On 30-May-2016 21:24, Andrei Alexandrescu wrote:
On 05/30/2016 12:34 PM, Jack Stouffer wrote:
On Monday, 30 May 2016 at 16:25:20 UTC, Nick Sabalausky wrote:
D1 -> D2 was a vastly more disruptive change than getting rid of
auto-decoding would be.
Don't be so sure. All string handling code
On 05/30/2016 12:34 PM, Jack Stouffer wrote:
On Monday, 30 May 2016 at 16:25:20 UTC, Nick Sabalausky wrote:
D1 -> D2 was a vastly more disruptive change than getting rid of
auto-decoding would be.
Don't be so sure. All string handling code would become broken, even if
it appears to work at
