Goto skips declaration

[Michelle Long]

On Saturday, 3 November 2018 at 21:55:56 UTC, lithium iodate 
wrote:
> On Saturday, 3 November 2018 at 21:36:08 UTC, Michelle Long 
> wrote:
>> No, the problem actually exists. Simply because a simplified 
>> example does not produce the result does not mean it doesn't 
>> exist. The compiler does a lot of things so to suggest that I 
>> simply fabricated the error because the simplified 
>> demonstration case does not produce the error as pathetic.
>>
>> I got this error in my code and I simplified all the crap out 
>> of it to what I did that produced it and how I remedied it. 
>> It's not my fault you don't believe me.
>
> That's simply the to us accessible evidence speaking against 
> you. Check out DustMite if you haven't already, it's a tool for 
> automatically reducing code while maintaining a user-defined 
> condition, such as the equivalence of compiler output.
> This thread will get nowhere as long as nobody can reproduce 
> the issue.

Look, sometimes it is nearly impossible to reduce because the 
problem is far more complicated... also compilers do a lot of 
hacky shit like optimization or rewriting things that then hide 
the error when reduced.

To try and act like it is my fault is ridiculous. Dustmite 
doesn't work. This is typical of dmd where nothing ever works as 
expected but the core group of people always seem to point 
fingers and expect the outsiders to deal with the mess they make.

Do people here expect me to find all the bugs for D? Also expect 
me to fix them? Write proper tooling? Where does it end?

When can someone just come in and say I've experienced a bug, 
this is what it `looks` like and then move on?


The fact is, I explained the simple case and gave the error. This 
proves that either DMD has an issue or it has an issue.

Building Win32\Debug\Demo.exe...
test.d(164): Error: `goto` skips declaration of variable

And when I simply wrap what follows in a block it compiles!

That is enough to PROVE there is a bug somewhere. Either it is an 
issue with goto or some other compiler bug or a complex 
combination of problems, but all due to dmd.

The fact that I can't produce a simple test case for others does 
not disprove this. The example I gave wasn't meant for a test 
case but to outline the problem. I thought it was a grammar 
related language decision. Either way, I would expect the 
"experts" to be able to figure out the real underlying issue 
immediately or after a few minutes of work. I guess I expect to 
much?

But what happens is the flood of the tyrants who demand that I 
stop everything I'm doing and produce a test case that has the 
same bug so they can be convinced that such a bug exists come 
marching in! It's not like any of them(or almost) will do 
anything to fix the bug. In fact, many will say it's not a bug 
but a feature.

In fact, given how long it takes for many bugs to get fixed in 
the D world(on the order of years), it is pointless.