Uncallable delegates

[Timon Gehr]

On 5/16/26 04:45, Richard (Rikki) Andrew Cattermole wrote:
> On Saturday, 16 May 2026 at 02:02:42 UTC, Walter Bright wrote:
>> Thank you. It suggests to me like the problem is with the pure 
>> inheritance.
>>
>> I suggest asking Gemini if it can reproduce the problem without a 
>> `pure` annotation.
>>
>> Or at least if it can craft a simpler example of the problem.
> 
> To agree with Walter here,

Walter is clearly just speculating, and his speculation is wrong.

> if there are problems with pure

No, there are problems with delegate context type checking. But type 
system features are not broken in isolation, soundness is a global property.

> please split  them off into their own ticket.
> ...

Rest assured my example is exactly in the right place in this thread.

> Please focus on const storage class & type qualifier in this proposal.
> ...

Please don't try to direct what we are allowed to talk about when you 
don't understand the technical details, otherwise you are just 
exacerbating the confusion. It is clear you have not read Dukc's DIP.

> Inferrable attributes that are modelling effects such as nothrow @nogc 
> pure scope and return are all on my list to be removed at a later date 
> due to their inability to work correctly due to dmd's architecture.
> 
> This is one of the main reasons (but not the only one) for the term 
> "attribute soup" that is a bane of many D developer.

I don't understand why you are swooping in to ostensibly tell us to stay 
on topic when I am on topic and you are wildly off topic. x)