What are the worst parts of D?

[Vladimir Panteleev via Digitalmars-d]

On Wednesday, 24 September 2014 at 04:36:33 UTC, Walter Bright 
wrote:
> On 9/23/2014 9:08 PM, Vladimir Panteleev wrote:
>> On Wednesday, 24 September 2014 at 03:59:10 UTC, Walter Bright 
>> wrote:
>>> This is completely unworkable.
>>
>> Mister, please stop hurting the pool straw man.
>>
>> Let me quote the relevant part:
>>
>>>>> They don't necessarily need to be blocking, just a notice 
>>>>> "hey, your PR
>>>>> broke this and that project" would surely be helpful to 
>>>>> detect the breakages
>>>>> early on.
>>
>> I think that aside from the technical limitations, that's 
>> completely reasonable,
>> and does not put any undue obligation on anyone.
>
> Who is going to maintain the autotester version of these 
> projects?
>
> What I'd like to see is the autotester regularly build release 
> packages out of HEAD. Then, large project maintainers can 
> create their own scripts to download the latest compiler and 
> attempt to build their project.

We've been talking about this since last year's DConf. I don't 
know if it's ever going to happen, but now there is Digger, which 
solves most of the same problem.

Nevertheless, this is not enough. It must be automatic - it must 
verify the state of things daily, without human intervention. 
It's unreasonable (borderline absurd, even) to expect that every 
large project maintainer to manually verify if their project 
still works every day.

It doesn't need to run on the same hardware as the autotester. It 
can run on the project maintainers' servers or home computers. 
But it must be easy to set up, and it should notify both the 
project owners and the pull request authors.