tg counter robustness

[monkyyy]

On Friday, 30 May 2025 at 14:12:20 UTC, Dukc wrote:
> On Friday, 30 May 2025 at 13:35:07 UTC, monkyyy wrote:
>> On Friday, 30 May 2025 at 10:08:54 UTC, Dukc wrote:
>>> So there's no point in discussing what should make the unit 
>>> test to pass or fail.
>>
>> I currently believe nothing does and this is a highly flexible 
>> feature thats been in the compiler for years
>
> Doesn't matter. Whatever it does currently does isn't meant to 
> be relied upon. It might change at any time.

The rate of development is SLOW, and the change if there is one 
will be to just break this(out of spite of me having too much fun)

It doesn't matter what the spec says, what matters is how quickly 
and easily the feature works, this is *higher* on my list then 
delegates, because delegates are fundamentally broken and a 
#wontfix. If it starts out buggy, it will likely remain buggy 
even after years of whack a mole.

Features implemented by accident are among the best because they 
are pathologically simple if bad api

> Or are you opining that this particular hack _should_ be 
> defined behaviour? If, what exactly should be guaranteed and 
> why?

Ive asked for any and every compile time side effect. I think we 
should drop the pretense that templates are sane, stable and pure.