VisualD regressions are severe; what do we do about critical infrastructure?

[monkyyy]

On Wednesday, 30 October 2024 at 14:10:42 UTC, Elias (0xEAB) 
wrote:
> 
> How would you like to get them into the standard library if not 
> by sending them through the regular PR process?

I think your misunderstanding all three of my points

1) I dont use git expect as a requirement, such as github; yet I 
use github still if lazily

2) there could be a higher success rate for long term integration 
of first time contributors

3) there could be a reciprocation feedback loop; i.e. if my bugs 
got fixed I would spend more time on bug reports instead of 
workarounds and defensive syntax testing

These are conditional, not absolutes.

> (Even for someone else to pick them up, they’d otherwise have 
> to stumble over your links here in the newsgroup instead of 
> just having a look at the open PRs.)

Am I suppose to care if they are seen then discarded?

I believe 4 things would drastically improve the std which are 
trivial to write

1) merging data structures litterally ever
2) simplifying the clunky meta-programming templates
3) renaming passes/lazy clarifying of some horribly formal docs
4) inclusion of "trivial" one liner algorithms that are 
composites of other range functions

These suggestions are met with:

1) allocator are super important/ship on dub
2) templates are not important for v3
~~3) (havnt pushed on this one much, but renaming one of the 
`std.write`s would be a breaking change)~~
4) "to travail"