Re: Driving Continuous Improvement in D

2018-06-05 Thread drug via Digitalmars-d-announce
05.06.2018 17:00, Steven Schveighoffer пишет: To clarify a bit, complicated or controversial changes that are likely to be delayed or stalled, should be split from simple doc changes if it turns out it's not going to be pulled anytime soon. But normally, adding fixes for docs I would think

Re: Driving Continuous Improvement in D

2018-06-05 Thread Steven Schveighoffer via Digitalmars-d-announce
On 6/5/18 9:58 AM, Steven Schveighoffer wrote: On 6/5/18 3:20 AM, drug wrote: 04.06.2018 21:08, Steven Schveighoffer пишет: On 6/4/18 1:51 PM, Joakim wrote: On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote: On 6/2/18 3:23 AM, Mike Parker wrote: [...] I like the article,

Re: Driving Continuous Improvement in D

2018-06-05 Thread Steven Schveighoffer via Digitalmars-d-announce
On 6/5/18 3:20 AM, drug wrote: 04.06.2018 21:08, Steven Schveighoffer пишет: On 6/4/18 1:51 PM, Joakim wrote: On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote: On 6/2/18 3:23 AM, Mike Parker wrote: [...] I like the article, but was taken aback a bit by this quote: "for

Re: Driving Continuous Improvement in D

2018-06-05 Thread drug via Digitalmars-d-announce
04.06.2018 21:08, Steven Schveighoffer пишет: On 6/4/18 1:51 PM, Joakim wrote: On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote: On 6/2/18 3:23 AM, Mike Parker wrote: [...] I like the article, but was taken aback a bit by this quote: "for example, a PR to fix a bug in a

Re: Driving Continuous Improvement in D

2018-06-04 Thread Steven Schveighoffer via Digitalmars-d-announce
On 6/4/18 1:51 PM, Joakim wrote: On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote: On 6/2/18 3:23 AM, Mike Parker wrote: [...] I like the article, but was taken aback a bit by this quote: "for example, a PR to fix a bug in a specific piece of code mustn’t also edit the

Re: Driving Continuous Improvement in D

2018-06-04 Thread Joakim via Digitalmars-d-announce
On Monday, 4 June 2018 at 15:52:24 UTC, Steven Schveighoffer wrote: On 6/2/18 3:23 AM, Mike Parker wrote: [...] I like the article, but was taken aback a bit by this quote: "for example, a PR to fix a bug in a specific piece of code mustn’t also edit the documentation of that function."

Re: Driving Continuous Improvement in D

2018-06-04 Thread Steven Schveighoffer via Digitalmars-d-announce
On 6/2/18 3:23 AM, Mike Parker wrote: In this post for the D Blog, Jack Stouffer details how dscanner is used in the Phobos development process to help improve code quality and fight entropy. The blog: https://dlang.org/blog/2018/06/02/driving-continuous-improvement-in-d/ reddit: https

Re: Driving Continuous Improvement in D

2018-06-02 Thread Jon Degenhardt via Digitalmars-d-announce
On Saturday, 2 June 2018 at 07:23:42 UTC, Mike Parker wrote: In this post for the D Blog, Jack Stouffer details how dscanner is used in the Phobos development process to help improve code quality and fight entropy. The blog: https://dlang.org/blog/2018/06/02/driving-continuous-improvement

Re: Driving Continuous Improvement in D

2018-06-02 Thread Microbe via Digitalmars-d-announce
On Saturday, 2 June 2018 at 13:32:00 UTC, Basile B. wrote: Microbe, if you were a keyword for a protection attribute in a programming language, i would choose "smuck". To borrow a quote from someone else on this forum.. knock of the sex talk!. Anyway, increased membrane permeability leads

Re: Driving Continuous Improvement in D

2018-06-02 Thread Basile B. via Digitalmars-d-announce
On Saturday, 2 June 2018 at 12:49:45 UTC, Microbe wrote: As you know, surrounding code within a module can infilitrate the membrane structure of those types that use 'private' to protect their boundary (for example, the 'private' member in that struct, in that blog). Since the compiler is

Re: Driving Continuous Improvement in D

2018-06-02 Thread Microbe via Digitalmars-d-announce
On Saturday, 2 June 2018 at 07:23:42 UTC, Mike Parker wrote: In this post for the D Blog, Jack Stouffer details how dscanner is used in the Phobos development process to help improve code quality and fight entropy. The blog: https://dlang.org/blog/2018/06/02/driving-continuous-improvement

Driving Continuous Improvement in D

2018-06-02 Thread Mike Parker via Digitalmars-d-announce
In this post for the D Blog, Jack Stouffer details how dscanner is used in the Phobos development process to help improve code quality and fight entropy. The blog: https://dlang.org/blog/2018/06/02/driving-continuous-improvement-in-d/ reddit: https://www.reddit.com/r/programming/comments