Manu Evans

Also, did you see this:  When I use the update button to check for DMD updates, it's been saying unavailable lately... maybe the DMD guys changed the URL pattern?

Okay, so I was trying to isolate what may be affecting it and I rebooted my computer to freshen up all the processes. The __debug* functions seem to be working...

I wouldn't worry too much. `emplace` will be deleted soon!

This is 12 years old. I only just noticed this, but now I've done an audit of my code and I found this affects me in several places! This is...

> as it would evaluate to a different value at different usage sites... How could it? The type of the function argument doesn't change at the call-site, unless it's a...

Syntax copy at the call-site is the only logical option that anyone would imagine; unless there's some really bad side effect of that, then we're violating the rule of least...

Also you could read that spec sentence several ways; like, the function to be called is resolved "in the context of the function declaration" (like, the scope used for resolution...

> > How could it? The type of the function argument doesn't change at the call-site, unless it's a template, but if the argument is T then it infers the...

> For a long time expressions containing those keywords would fail (e.g. `__FILE__.ptr` would point to the declaration file, not the call site file), but that has been fixed since...

I'm usually sceptical of tools like this. I can't see anything obviously wrong with the implementation, but in my experience, this sort of thing tends to encourage usage by non-experts...