Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: There's a lot of technical debt I've been trying to fix with that, and nobody else seems willing to do it. For example, fixing the error messages so they make use of color syntax highlighting. It's boring, tedious, unfun work,

Re: Some Observations on the D Development Process

On 1/9/2018 6:53 PM, Mike Franklin wrote: I couldn't find any cases like that. If you know of them, please explicitly identify them for me. I already fixed them.

Re: Some Observations on the D Development Process

On 01/11/2018 02:15 PM, Johan Engelen wrote: And I've been working for a long time on a fuzzing article. It's almost done! - Johan A fuzzy font would suit that article. :o) Ali

Re: Some Observations on the D Development Process

On Wednesday, 10 January 2018 at 05:46:04 UTC, Nicholas Wilson wrote: On Sunday, 7 January 2018 at 16:52:55 UTC, Random D user wrote: While not directly applicable to 'technical debt', has anyone ever written a fuzzer for dmd? Johan Engelen has used LLVM libFuzzer on it. And I've been

Re: Some Observations on the D Development Process

On Sunday, 7 January 2018 at 16:52:55 UTC, Random D user wrote: While not directly applicable to 'technical debt', has anyone ever written a fuzzer for dmd? Johan Engelen has used LLVM libFuzzer on it.

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 04:26:25 UTC, Walter Bright wrote: On 1/4/2018 9:44 AM, Jack Stouffer wrote: DMD also has at least 30 PRs which have had no action from the author in over a year. There's no reason these should be kept open; they just take up auto-tester resources and lower the

Re: Some Observations on the D Development Process

On Saturday, 6 January 2018 at 02:53:38 UTC, Walter Bright wrote: For example, there were several uses of the word 'ctor' instead of 'constructor'. I couldn't find any cases like that. If you know of them, please explicitly identify them for me. Thanks, Mike

Re: Some Observations on the D Development Process

On 7 January 2018 at 17:52, Random D user via Digitalmars-d wrote: > On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: >> >> On 1/4/2018 2:34 AM, Mike Franklin wrote: >>> >>> Walter seems to pop in daily, and occasionally reviews PRs, and his PRs >>> of

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: On 1/4/2018 2:34 AM, Mike Franklin wrote: Walter seems to pop in daily, and occasionally reviews PRs, and his PRs of late are mostly just refactorings rather than fixing difficult bugs. There's a lot of technical debt I've been

Re: Some Observations on the D Development Process

On Fri, 05 Jan 2018 18:53:38 -0800, Walter Bright wrote: > On 1/5/2018 7:39 AM, Seb wrote: >> We should put things like this somewhere where it can easily be seen by >> others. >> The obvious candidates are the Wiki and Bugzilla, but both have >> historically proven to yield poor results, e.g. >

Re: Some Observations on the D Development Process

On 1/5/2018 7:41 AM, H. S. Teoh wrote: I'm sad that it has to fall upon Walter to do these routine, mundane, tedious work, when we greatly need his expertise elsewhere in D land. Walter, what about posting a list of boring, tedious stuff that has landed on your plate somewhere, so that those of

Re: Some Observations on the D Development Process

On 1/4/2018 10:20 PM, Patrick Schluter wrote: The only people I ever saw with a flu (I mean a real influenza) had all one thing in common: they all had gotten the flu shot. There was a 3 month gap between the shot and getting the flu, so there's no credible connection. I haven't gotten the

Re: Some Observations on the D Development Process

On 1/5/2018 7:39 AM, Seb wrote: We should put things like this somewhere where it can easily be seen by others. The obvious candidates are the Wiki and Bugzilla, but both have historically proven to yield poor results, e.g. Sigh. Bugzilla is the answer, and lots of people do troll Bugzilla

Re: Some Observations on the D Development Process

On 1/5/2018 6:26 AM, Adam D. Ruppe wrote: For my projects, even if a PR isn't perfect, unless it is just plain bad or goes in a direction I strongly disagree with, I'll merge it anyway pretty quickly and just fix up the bits I don't like later myself. So if something is OK but not great

Re: Some Observations on the D Development Process

On Thu, Jan 04, 2018 at 07:28:10PM -0800, Walter Bright via Digitalmars-d wrote: > On 1/4/2018 2:34 AM, Mike Franklin wrote: > > Walter seems to pop in daily, and occasionally reviews PRs, and his > > PRs of late are mostly just refactorings rather than fixing > > difficult bugs. > There's a lot

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 04:20:06 UTC, Walter Bright wrote: On 1/4/2018 7:41 PM, Mike Franklin wrote: If you have simple, mundane work that needs to be done, make a list and send it my way; you should have my e-mail address.  But please be specific; "fix error messages" is just going to

Re: Some Observations on the D Development Process

On 1/5/18 9:26 AM, Adam D. Ruppe wrote: On Friday, 5 January 2018 at 10:08:11 UTC, John Colvin wrote: A perfect project would be able to make quick decisions on PRs, but that doesn't mean closing PRs makes a better project. It's a little bit cargo-culty. For my projects, even if a PR isn't

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 06:20:54 UTC, Patrick Schluter wrote: The only people I ever saw with a flu (I mean a real influenza) had all one thing in common: they all had gotten the flu shot. That's a case of selection bias: the people who get the shot tend to be those who are already at

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 10:08:11 UTC, John Colvin wrote: A perfect project would be able to make quick decisions on PRs, but that doesn't mean closing PRs makes a better project. It's a little bit cargo-culty. For my projects, even if a PR isn't perfect, unless it is just plain bad or

Re: Some Observations on the D Development Process

On 1/5/18 5:08 AM, John Colvin wrote: On Friday, 5 January 2018 at 04:26:25 UTC, Walter Bright wrote: I can't agree with the "just close older bugs and PRs." There's good stuff in them. Even if the PR is no good, it provides insight to someone working on a better fix. Closing it means nobody

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 04:26:25 UTC, Walter Bright wrote: I can't agree with the "just close older bugs and PRs." There's good stuff in them. Even if the PR is no good, it provides insight to someone working on a better fix. Closing it means nobody will ever be aware of it or look at it

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: Another issue is I've had the flu for a while which makes me tired, and then it's best to work on things that don't require much mental energy. I quess that applies easily twice as strongly if you code bigger things on the run,

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: On 1/4/2018 2:34 AM, Mike Franklin wrote: Walter seems to pop in daily, and occasionally reviews PRs, and his PRs of late are mostly just refactorings rather than fixing difficult bugs. There's a lot of technical debt I've been

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 04:14:57 UTC, Steven Schveighoffer wrote: On 1/4/18 10:28 PM, Walter Bright wrote: (Yes, I got the flu shot, and the durned thing did not work.) I had a flu shot once in my adult life. Never been sicker. Won't ever get it again. The only people I ever saw with

Re: Some Observations on the D Development Process

On 1/4/2018 9:44 AM, Jack Stouffer wrote: DMD also has at least 30 PRs which have had no action from the author in over a year. There's no reason these should be kept open; they just take up auto-tester resources and lower the signal to noise ratio. If the author comes back later, they can

Re: Some Observations on the D Development Process

On 1/4/2018 7:41 PM, Mike Franklin wrote: If you have simple, mundane work that needs to be done, make a list and send it my way; you should have my e-mail address.  But please be specific; "fix error messages" is just going to get a reply from me asking questions. Ok, fix error messages,

Re: Some Observations on the D Development Process

On 1/4/18 10:28 PM, Walter Bright wrote: (Yes, I got the flu shot, and the durned thing did not work.) I had a flu shot once in my adult life. Never been sicker. Won't ever get it again. -Steve

Re: Some Observations on the D Development Process

On Friday, 5 January 2018 at 03:28:10 UTC, Walter Bright wrote: There's a lot of technical debt I've been trying to fix with that, and nobody else seems willing to do it. For example, fixing the error messages so they make use of color syntax highlighting. It's boring, tedious, unfun work,

Re: Some Observations on the D Development Process

On 1/4/2018 2:34 AM, Mike Franklin wrote: Walter seems to pop in daily, and occasionally reviews PRs, and his PRs of late are mostly just refactorings rather than fixing difficult bugs. There's a lot of technical debt I've been trying to fix with that, and nobody else seems willing to do it.

Re: Some Observations on the D Development Process

On Thu, Jan 04, 2018 at 06:50:25PM +, Dmitry Olshansky via Digitalmars-d wrote: > On Thursday, 4 January 2018 at 18:09:32 UTC, Seb wrote: [...] > > BTW: For those who haven't seen this, dlang-bot now detects these > > stalled PRs and for now labels them as "stalled": > > > >

Re: Some Observations on the D Development Process

On Thursday, 4 January 2018 at 18:09:32 UTC, Seb wrote: On Thursday, 4 January 2018 at 17:44:58 UTC, Jack Stouffer wrote: DMD also has at least 30 PRs which have had no action from the author in over a year. There's no reason these should be kept open; they just take up auto-tester resources

Re: Some Observations on the D Development Process

On Thursday, 4 January 2018 at 17:44:58 UTC, Jack Stouffer wrote: DMD also has at least 30 PRs which have had no action from the author in over a year. There's no reason these should be kept open; they just take up auto-tester resources and lower the signal to noise ratio. FYI: stalled PRs

Re: Some Observations on the D Development Process

On Thursday, 4 January 2018 at 10:34:05 UTC, Mike Franklin wrote: A few of us are working hard to revive old PRs and either see them across the finish line, or give them a quick path to closure. 2 months ago the DMD PR queue stood at about 190. Now it's hovering between 140 and 150. DMD

Re: Some Observations on the D Development Process

On Thu, 04 Jan 2018 10:34:05 +, Mike Franklin wrote: > This is in response to some of the frustrations offered in the thread > staring with > http://forum.dlang.org/post/oeigdutfphxhenexc...@forum.dlang.org > > I share some of those frustrations, and I've been vocal about such > things

Some Observations on the D Development Process

This is in response to some of the frustrations offered in the thread staring with http://forum.dlang.org/post/oeigdutfphxhenexc...@forum.dlang.org I share some of those frustrations, and I've been vocal about such things myself. However, in the last 2 months, at least in terms of the DMD