On Tuesday, 3 November 2015 at 14:35:08 UTC, Andrei Alexandrescu
wrote:
https://goo.gl/r24Izw
Some of them are D1 only; I'll make an executive decision about
those soon. Some of them have been fixed or obviated by recent
improvements. And finally the bulk of them need a little work
each to get them fixed.
I'm thinking this has crowdsourcing written all over it. It
would be great if many of us made one pass through the list and
take a look at bugs with an eye for cleaning up the list.
Andrei
I skimmed through the list, looking for easy starters. This is
what in the end held me back:
- comment saying how a bug-fix will break code
- unfinished discussion about how its not a bug, (or how to solve
it, e.g. https://issues.dlang.org/show_bug.cgi?id=14485)
- halfway fixes and no clear path how to fix the other half (e.g.
https://issues.dlang.org/show_bug.cgi?id=4391, curry was renamed
to partial to avoid confusion. Now do we still want curry?)
- unclear goals (e.g.
https://issues.dlang.org/show_bug.cgi?id=4656 `Let's keep it
opened until the error message is fixed.`)
I do not know what to do with that stuff. In most cases I figure
they require an executive decision.
What I can do is go through the list and recommend bugs to be
closed/wontfix.
