on Tue Feb 17 2009, Sohail Somani <sohail-AT-taggedtype.net> wrote:
David Abrahams wrote:
on Tue Feb 17 2009, Sohail Somani <sohail-AT-taggedtype.net> wrote:
This comes back to a question I had earlier which was: where in the standard does it specify that looking up functions during ADL requires instantiation of return types?
Well, if the type is illegal in a way that doesn't qualify for SFINAE, a diagnostic is required. That means the compiler has to figure out what the type is. However, I think the real question is whether the code is required to cause the overload resolution at all. Strictly speaking, the code can be considered to be "unused" and so the compiler is allowed to not instantiate it.
This is most likely the cause.
I thought it was kind of funny that I reported the same issue in two different compilers. Unfortunately, no workaround or fix yet!
Huh? 1711 was fixed and closed.
Sorry, I was not clear. I meant no workaround or fix for the second compiler.
What 2nd compiler? I thought you meant two versions of GCC. If you mean Sun, then AFAIK that's a recent report, and **it's not the same issue**. -- Dave Abrahams BoostPro Computing http://www.boostpro.com