please help me submit a bug!

[jfondren]

On Friday, 8 October 2021 at 18:30:28 UTC, Basile.B wrote:
> On Friday, 8 October 2021 at 15:53:40 UTC, jfondren wrote:
>> On Friday, 8 October 2021 at 15:51:53 UTC, Basile B. wrote:
>>> You've replied to the wrong person.
>>
>> I haven't. These two lines are a reply to you:
>>
>>>> only one of those array literals involves the GC, so it 
>>>> would be pretty annoying for the compiler to not point it 
>>>> out.
>
> Who said that the compiler should not point the problem out ?

Nobody said that the compiler *should* not point the problem out, 
but workman, in the beginning of this thread, said that the 
compiler *did* not point the problem out:

>The problem is there is no easy way to find which line cause 
>this error:
>...
>This function is huge, I hope compiler can print the the lines.

You then said

>Why do you think that there is a bug ?

>D array literals are dynamic arrays, so the GC is used.

Which I interpreted to mean that you reckon the problem should be 
trivial to find even with the compiler not pointing it out, 
because the problem will be a D array literal which all use the 
GC.

In reply to that, I showed you some code with five D array 
literals, only one of which uses the GC. If workman's huge 
function has many D array literals and he's already tried going 
through them to find the problem and hasn't yet, he might have a 
haystack like this to sort through.

One of these is probably the case:

1. workman overlooked the line number in the error output--there 
is no bug

2. workman did not overlook the line number but thinks it not 
helpful enough. By "I hope compiler can print the lines" he means 
that he wants more verbose output that points to the array 
literal in context and explains why it uses the GC.

3. there is a bug and the compiler sometimes doesn't print the 
error number.

There are a lot of possibilities but the thread still isn't a 
mystery novel.