Unittest Absurdity

[frame]

On Friday, 5 August 2022 at 21:24:13 UTC, Steven Schveighoffer 
wrote:

> That's not what I was talking about here. I'm talking about 
> `-vcg-ast` not telling you how it's calling the function.

Thanks for clarification.

I had that in mind but wasn't sure. I first thought it just get 
optimized away and in case of name/type collision would create 
another name for the function but after testing with `static if` 
it really shows that this assumption was wrong :D