Thread overview
Years-old debts in the language/compiler/docs
May 05, 2022
Tejas
May 12, 2022
Walter Bright
May 04, 2022

It is quite discouraging to see things here and there being abandoned.

Example 1:

https://dlang.org/spec/hash-map.html#static_initialization

Quick git blame: linked example was written SIX YEARS ago, note about it being not implemented - THREE YEARS ago. Does no one care that language reference contains examples that are not actually valid?

Example 2:

https://dlang.org/spec/function.html#property-functions

Another quick git blame: spec of property functions was documented SEVEN YEARS ago, warning about it being reviewed and discouraged to use - FOUR YEARS ago. It takes quite too long to start and finish the review process that way, don't you think?

Example 3:

https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1014.md (accepted in 2018, has no implementation mark)
https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1030.md (accepted in 2020, has no implementation mark)
...and some newer that probably can be in works.

What is the point of accepting proposals if they stay non-implemented for years?

It can also go further to things like std.experimental.logger being "experimental" for 7 years now but I believe it has something to do with "phobos v2" and stuff.

May 05, 2022

On Wednesday, 4 May 2022 at 17:46:35 UTC, Vladimir Marchevsky wrote:

>

It is quite discouraging to see things here and there being abandoned.

Example 1:

https://dlang.org/spec/hash-map.html#static_initialization

Quick git blame: linked example was written SIX YEARS ago, note about it being not implemented - THREE YEARS ago. Does no one care that language reference contains examples that are not actually valid?

Example 2:

https://dlang.org/spec/function.html#property-functions

Another quick git blame: spec of property functions was documented SEVEN YEARS ago, warning about it being reviewed and discouraged to use - FOUR YEARS ago. It takes quite too long to start and finish the review process that way, don't you think?

Example 3:

https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1014.md (accepted in 2018, has no implementation mark)
https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1030.md (accepted in 2020, has no implementation mark)
...and some newer that probably can be in works.

What is the point of accepting proposals if they stay non-implemented for years?

It can also go further to things like std.experimental.logger being "experimental" for 7 years now but I believe it has something to do with "phobos v2" and stuff.

DIP 1014 has actually been superseded by DIP 1040, but something happened and the author has stopped development for the time being, AFAIK

The named parameters DIP is actually progressed quite a bit, but there are problems dealing with overloads, IIRC.

Either make a forum post(in general) asking about the progress on these two or ask on the community Discord (I recommend the latter)

It's frustrating to see these things lag, but that's just what it means to be (almost)completely volunteer driven 😓

And, you know what they say in open source fashion: if you're complaining about it, fix it(this tends to aggravate the poster even further, usually, so please don't think that I'm telling you to do it since you're complaining)

idk about the rest

May 11, 2022
On 5/4/2022 10:46 AM, Vladimir Marchevsky wrote:
> It is quite discouraging to see things here and there being abandoned.
> 
> Example 1:
> 
> https://dlang.org/spec/hash-map.html#static_initialization
> 
> Quick git blame: linked example was written SIX YEARS ago, note about it being not implemented - THREE YEARS ago. Does no one care that language reference contains examples that are not actually valid?

https://issues.dlang.org/show_bug.cgi?id=23103


July 29, 2022

On Wednesday, 4 May 2022 at 17:46:35 UTC, Vladimir Marchevsky wrote:

>

It is quite discouraging to see things here and there being abandoned.

There are tons of improvements happening all the time done by various contributors. I'm sure you can find other examples of things that don't seem to get improved, but the truth is that building a language ecosystem is pretty big endeavor (*) and there will always be parts that seem under developed. I suggest you observe the awesome work that many contributors are pouring in, before jumping to conclusions:

Check the changelog for the last 5-10 major releases:

Language implementation:

Language documentation:

Dub package manager

As for std.experimental.logger, it's currently in the process being promoted out of experimental:

(*) this is not an excuse. All issues that you pointed are real and must be taken care of. I'm just saying that you should adjust your expectations based on the scope of a project like this and the contributor's priorities and available time.