D has become unbearable and it needs to stop

[H. S. Teoh]

On Thu, Jun 08, 2023 at 02:56:21PM +0000, GrimMaple via Digitalmars-d wrote:
[...]
> The buildkite link is a joke in itself. It has some random packages,
> many of which are either deprecated, either abandoned. It doesn't even
> include most of the https://code.dlang.org/?sort=score list.

Here's a wild idea:
- Go through code.dlang.org and compile them with the latest compiler.
- Add *every* project that compiles to the buildkite list.
- Repeat this every release cycle.
- In the meantime, if anyone comes across any D project anywhere, as
  long as the source is public add it to buildkite.

OK, that takes care of coverage. By this point the core devs are
probably already screaming, "who's gonna fix broken builds when an
unmaintained project stops compiling?"

My answer is:
- For every buildkite breakage, contact the maintainer and ask him to
  fix the code.
- If he doesn't respond (the project is abandoned / inactive), the PR
  submitter should figure out a way of fixing / working around the
  problem.  THEN ADD THE WORKAROUND TO THE COMPILER. Either offer a flag
  to enable the workaround, or have the compiler generate an error
  message with explicit instructions of how to fix the problem.


The idea as presented above is probably impractical for a ton of
reasons. But it's a starting point. Somewhere to begin taking practical
steps attacking this problem, rather than sweeping it under the rug or
just yelling at each other.


T

-- 
Let X be the set not defined by this sentence...