Re: Let's talk about deprecations

2017-07-03 Thread bachmeier via Digitalmars-d
On Monday, 3 July 2017 at 16:51:47 UTC, Cym13 wrote: I don't get it: how is linking old and unmaintained code "fixing" anything? Dead code is dead, if it's been two years already let it die and fix your own, anything else can't be future-proof. I don't understand your comment. I'm

Re: Let's talk about deprecations

2017-07-03 Thread Seb via Digitalmars-d
On Monday, 3 July 2017 at 16:47:35 UTC, Iain Buclaw wrote: Can we tag compiler versions in dub? I think you have such a construct in npm... Found it, https://docs.npmjs.com/files/package.json#engines Yeah - compiler, os, and cpu all seem like something that should be made available in the

Re: Let's talk about deprecations

2017-07-03 Thread Cym13 via Digitalmars-d
On Monday, 3 July 2017 at 16:08:43 UTC, bachmeier wrote: On Monday, 3 July 2017 at 13:14:02 UTC, Jonathan M Davis wrote: So, in general, I think that it's a big mistake to keep deprecated stuff along on a permanent or semi-permanent basis. Keeping it around for about two years like we do now

Re: Let's talk about deprecations

2017-07-03 Thread Iain Buclaw via Digitalmars-d
On 3 July 2017 at 01:48, Nicholas Wilson via Digitalmars-d wrote: > On Sunday, 2 July 2017 at 23:27:26 UTC, Seb wrote: >> >> Proposals >> - >> >> I think we should learn from the past. Here are a couple of ideas: >> >> 1) Stop making such a fuzz about having a

Re: Let's talk about deprecations

2017-07-03 Thread bachmeier via Digitalmars-d
On Monday, 3 July 2017 at 13:14:02 UTC, Jonathan M Davis wrote: So, in general, I think that it's a big mistake to keep deprecated stuff along on a permanent or semi-permanent basis. Keeping it around for about two years like we do now is already quite a long time in that regard. As long as

Re: Let's talk about deprecations

2017-07-03 Thread Jonathan M Davis via Digitalmars-d
On Monday, July 03, 2017 13:04:46 bachmeier via Digitalmars-d wrote: > On Monday, 3 July 2017 at 11:30:14 UTC, Jonathan M Davis wrote: > > Ultimately, the way that folks find out about needing to change > > their code is compiling it and seeing the deprecation messages > > - or getting compilation

Re: Let's talk about deprecations

2017-07-03 Thread bachmeier via Digitalmars-d
On Monday, 3 July 2017 at 11:30:14 UTC, Jonathan M Davis wrote: Ultimately, the way that folks find out about needing to change their code is compiling it and seeing the deprecation messages - or getting compilation errors if they wait too long, but that's a _lot_ more of a pain to deal with

Re: Let's talk about deprecations

2017-07-03 Thread Jonathan M Davis via Digitalmars-d
On Sunday, July 02, 2017 23:27:26 Seb via Digitalmars-d wrote: > Hi all, > > I think we need to talk about deprecations. > A recent example on [Phobos][#5532] uncovered an ugly truth: many > people don't seem care about deprecation warnings. > > #5532 wanted to remove the symbols scheduled for

Re: Let's talk about deprecations

2017-07-02 Thread Vladimir Panteleev via Digitalmars-d
On Sunday, 2 July 2017 at 23:27:26 UTC, Seb wrote: 1) Stop making such a fuzz about having a long deprecation period. Most people will only care about a deprecation when their project doesn't compile anymore. A deprecation period of two releases is more than enough for users that care. As seen

Re: Let's talk about deprecations

2017-07-02 Thread Nicholas Wilson via Digitalmars-d
On Sunday, 2 July 2017 at 23:27:26 UTC, Seb wrote: Proposals - I think we should learn from the past. Here are a couple of ideas: 1) Stop making such a fuzz about having a long deprecation period. Most people will only care about a deprecation when their project doesn't compile

Let's talk about deprecations

2017-07-02 Thread Seb via Digitalmars-d
Hi all, I think we need to talk about deprecations. A recent example on [Phobos][#5532] uncovered an ugly truth: many people don't seem care about deprecation warnings. #5532 wanted to remove the symbols scheduled for deprecation - most noteworthy here the removal of std.c. FYI std.c was