On Monday, 2 April 2018 at 13:55:25 UTC, bachmeier wrote:
No, the reason nothing gets done is because "that would break code" is used to kill every proposal that comes along. Someone that only responds to proposals with "write a DIP" proceeds to announce a major piece of the language will be deprecated without writing a DIP himself. Corporate leadership doesn't work with an open source project. I could have gotten more involved long ago, but I'd rather not jump on a ship that's sailing in circles. From the many comments I've seen, I'm not the only one.
Andrei wrote in the message
I am looking for folks to assist me in creating a DIP for that. There will be a _lot_ of work involved, so don't take it lightly.
So, let's keep the discussion factual. I'm pretty sure that every aspect will be taken in account and pondered prior to a decision.
I'm +1 on major breaking changes if they drive D towards a better shape.
/Paolo
