Getting action on your favorite D issues

[Patrick Schluter]

On Friday, 5 June 2020 at 21:57:39 UTC, ag0aep6g wrote:
> On 05.06.20 22:35, Walter Bright wrote:
>> 1. File bugzilla issue for them. Issues not in bugzilla don't 
>> get fixed.
> [...]
>> Bring them up now and then.
>
> How frequent is "now and then"? Like, once a month? Once a year?
>
> Ideally, you would be prioritizing issues based on severity and 
> impact. If you only fix the issues that people nag you about, 
> you risk leaving serious bugs unattended.
>
> Anyway, here are some personal favorites:
>
>
> 1) The DIP 1000 implementation has a glaring accepts-invalid 
> bug with `pure` functions.
> https://issues.dlang.org/show_bug.cgi?id=20150
>
> In my opinion, this one is a blocker for DIP 1000. And 
> unfortunately, it probably made DIP 1000 look better than it is.
>
>
> 2) "bool can be both true and false"
> https://issues.dlang.org/show_bug.cgi?id=20148
>
> This one is just silly.

Undefined behaviour. This said, there is a real code generation 
error in dmd (not in gdc and ldc) as H.S.Teoh noticed which 
manifests only in non optimized code. It's in the parameter 
passing of bool values to a function. It should use the zero 
extending mov instruction instead. The bug happens only with 8 
bit sized types (bool, byte, ubyte and char). With short it uses 
correctly the movzx instruction.

>
>
> 3) DMD's codegen for the BT (bit test) instruction is all kinds 
> of wrong.
> https://issues.dlang.org/show_bug.cgi?id=18750
>
> A testimony for the questionable quality of DMD's backend.
>
>
> 4) "import doesn't verify module declaration"
> https://issues.dlang.org/show_bug.cgi?id=15086
>
> This accepts-invalid (and arguably wrong-code) issue had some 
> lively discussion years ago. There was a PR, the issue was 
> closed as invalid, it was reopened. And finally it was 
> forgotten.
>
>
> 5) std.stdio tries converting between different UTF variants, 
> but fails horribly.
> https://issues.dlang.org/show_bug.cgi?id=18789 and
> https://issues.dlang.org/show_bug.cgi?id=18801
>
> I tried fixing this one but got stuck when I couldn't reproduce 
> the failures on Windows that the auto-tester shows.