On Friday, 9 March 2018 at 06:14:05 UTC, Jonathan M Davis wrote:
We'll make breaking changes if we judge the gain to be worth
the pain, but we don't want to be constantly breaking people's
code, and some changes are large enough that there's arguably
no justification for them, because they w
On Wednesday, 7 March 2018 at 17:11:55 UTC, H. S. Teoh wrote:
Kill autodecoding, I say. Kill it with fire!!
T
Please!!!
On Thursday, 8 March 2018 at 17:35:11 UTC, H. S. Teoh wrote:
Yeah, the only reason autodecoding survived in the beginning
was because Andrei (wrongly) thought that a Unicode code point
was equivalent to a grapheme. If that had been the case, the
cost associated with auto-decoding may have been
On Friday, March 09, 2018 03:16:03 Taylor Hillegeist via Digitalmars-d
wrote:
> I wasn't so much asking about auto-decoding in particular more
> about the mentality and methods of breaking changes.
>
> In a way any change to the compiler is a breaking change when it
> comes to the configuration.
On Thursday, 8 March 2018 at 17:14:16 UTC, Jonathan M Davis wrote:
On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via
Digitalmars-d wrote:
On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis
wrote:
> On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via
>
> Digitalmars-d wr
On Thursday, 8 March 2018 at 17:35:11 UTC, H. S. Teoh wrote:
On Thu, Mar 08, 2018 at 10:14:16AM -0700, Jonathan M Davis via
Digitalmars-d wrote:
[...]
[...]
[...]
[...]
Yeah, the only reason autodecoding survived in the beginning
was because Andrei (wrongly) thought that a Unicode code poin
On Thu, Mar 08, 2018 at 10:14:16AM -0700, Jonathan M Davis via Digitalmars-d
wrote:
> On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via Digitalmars-d
> wrote:
[...]
> > I'd agree with you, hate the special casing. However it seems to
> > me this has been debated to death already, and that
On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via Digitalmars-d
wrote:
> On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis
>
> wrote:
> > On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via
> >
> > Digitalmars-d wrote:
> >> On Wednesday, 7 March 2018 at 06:00:30 UTC, Tayl
On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis
wrote:
On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via
Digitalmars-d wrote:
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
> That way the breaking change was easily fixable, and the
> mistakes of the
On Wednesday, 7 March 2018 at 16:29:33 UTC, Seb wrote:
Well, I tried that already:
https://github.com/dlang/phobos/pull/5513
In short: very easy to do, but not much interest at the time.
No. The main problem with that (and the idea of using a compiler
flag in general) is that it affects the
On Wednesday, 7 March 2018 at 16:33:25 UTC, Seb wrote:
On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt
wrote:
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
[...]
Auto-decoding is a significant issue for the applications I
work on (search engines). There is a
On Wed, Mar 07, 2018 at 04:29:33PM +, Seb via Digitalmars-d wrote:
> On Wednesday, 7 March 2018 at 14:59:35 UTC, Steven Schveighoffer wrote:
> > On 3/7/18 1:00 AM, Taylor Hillegeist wrote:
> > > [...]
> >
> > Note, autodecoding is NOT a feature of the language, but rather a
> > feature of Phob
On Wed, Mar 07, 2018 at 04:33:25PM +, Seb via Digitalmars-d wrote:
> On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt wrote:
[...]
> > Auto-decoding is a significant issue for the applications I work on
> > (search engines). There is a lot of string manipulation in these
> > environme
On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt wrote:
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
[...]
Auto-decoding is a significant issue for the applications I
work on (search engines). There is a lot of string manipulation
in these environments, and
On Wednesday, 7 March 2018 at 14:59:35 UTC, Steven Schveighoffer
wrote:
On 3/7/18 1:00 AM, Taylor Hillegeist wrote:
[...]
Note, autodecoding is NOT a feature of the language, but rather
a feature of Phobos.
It would be quite interesting I think to create a modified
phobos where autodecodin
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
So i've seen on the forum over the years arguments about
auto-decoding (mostly) and some other things. Things that have
been considered mistakes, and cannot be corrected because of
the breaking changes it would create. And I a
On 3/7/18 1:00 AM, Taylor Hillegeist wrote:
So i've seen on the forum over the years arguments about auto-decoding
(mostly) and some other things. Things that have been considered
mistakes, and cannot be corrected because of the breaking changes it
would create. And I always wonder why not make
On Wednesday, March 07, 2018 13:40:20 Nick Treleaven via Digitalmars-d
wrote:
> On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis
>
> wrote:
> > I'd actually argue that that's the lesser of the problems with
> > auto-decoding. The big problem is that it's auto-decoding. Code
> > points
On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis
wrote:
I'd actually argue that that's the lesser of the problems with
auto-decoding. The big problem is that it's auto-decoding. Code
points are almost always the wrong level to be operating at.
For me the fundamental problem is havi
On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via Digitalmars-d
wrote:
> On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
>
> wrote:
> > That way the breaking change was easily fixable, and the
> > mistakes of the past not forever. Is it just the cost of
> > maintenance?
>
>
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
That way the breaking change was easily fixable, and the
mistakes of the past not forever. Is it just the cost of
maintenance?
auto-decoding problem was mostly that it couldn't be @nogc since
throwing, but with further relea
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist
wrote:
So i've seen on the forum over the years arguments about
auto-decoding (mostly) and some other things. Things that have
been considered mistakes, and cannot be corrected because of
the breaking changes it would create. And I a
For what it's worth, I like autodecoding.
I worry we could be in a situation where a moderate number of
people are strong opponents and a lot of people are weak fans,
none of which individually care enough to post. Hopefully the D
survey results will shed some light on this, though I don't
re
So i've seen on the forum over the years arguments about
auto-decoding (mostly) and some other things. Things that have
been considered mistakes, and cannot be corrected because of the
breaking changes it would create. And I always wonder why not
make a solution to the tune of a flag that makes
24 matches
Mail list logo
