On 5/23/2022 6:46 AM, FeepingCreature wrote:
> IMO, fear of breaking things is for projects who think they already have the most users that they will ever have. If you anticipate more people using D in the future, you should not let the complaints of current users cause pain for future users.

Fixes for outright bugs that wind up breaking peoples' code is an unfortunate cost, but one we'll just have to bear.


> At any rate, my personal oft-stated opinion is of course that the rate of change is too small. (Though I can't complain too loudly, since I've not exactly been making a lot of pull requests lately...)

Everyone has their own must-have favorite enhancement request. Unfortunately, they're all different!

On Tuesday, 24 May 2022 at 17:25:16 UTC, Walter Bright wrote:
>
> > Should D have co-routines or should async/await be
> implemented? Then we need a document that explains to everybody what needs to be implemented so people can go pick a certain work package they want to implement.
>
> I've suggested many times that someone should work on async/await. You're free to contribute there, too.

I don't think this is enough. "You are free to contribute" is not enough to motivate people. What is needed are work packages and also design documents so that they know the details what to implement. Having this also states the goals and vision of D.

Freely implementing something is no guarantee that it will be merged to the D main branch. A stated goal and implementation according to the design guarantees this which motivates people to contribute.

Not having written goals, designs and what should be done will just end up in a Half Life 3 situation.

On Tuesday, 24 May 2022 at 17:25:16 UTC, Walter Bright wrote:
> On 5/24/2022 2:58 AM, IGotD- wrote:
>> Right now people in the D project don't even know what to do or implement.
>
> They can visit bugzilla, pick anything open, and work on it.
>
> [snip]

There are only so many people who have the knowledge needed to fix DMD bugs...makes sense for those capable and interested in working on DMD to coordinate on what are the most important (TM) bugs/things to work on...

On 5/23/2022 10:30 AM, mee6 wrote:
> I don't know what to say when you have so many broken features that it becomes a regular occurrence that people become dependent on your broken features. Obviously something isn't working.

D is hardly unique in that aspect.

I've often had to deal with complaints that C code developed with Microsoft C/C++ wouldn't compile with my compiler, because MSC implemented the language contrary to the spec. I've seen it in Javascript, too, when I wrote Dscript.

On 5/22/2022 6:31 AM, deadalnix wrote:
> The problem here isn't that people aren't reporting these, or aren't writing DIP or whatever. It is that they are told to do so, waste their time doing that and then they get named argument instead.

I did a bugzilla search for every issue you have submitted:

https://issues.dlang.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&email1=deadalnix&emailreporter1=1&emailtype1=substring&list_id=240739&query_format=advanced&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=REMIND&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED

Every single one was resolved.

You are not wasting your time posting issues.

----------------------------

> I wrote DIP, they pretty much got ignored.

Here's a list of DIPs and their statuses:

https://github.com/dlang/DIPs/blob/master/DIPs/README.md

Which one is yours?

On 5/24/2022 10:58 AM, jmh530 wrote:
> There are only so many people who have the knowledge needed to fix DMD bugs...makes sense for those capable and interested in working on DMD to coordinate on what are the most important (TM) bugs/things to work on...

There's something for every skill level:

https://issues.dlang.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=240744&query_format=advanced