Re: [boost] [type traits extension] test for const volatile& as returntype

g++ is just fine for what I want to do but intel issues an error if T is "const volatile&" so that the program cannot compile and the g(...) is not chosen. Does anybody understands if this is the right behaviour according to the standard or if g++ is right chosing g(...)?

No idea, but if you have a test case I'm able to file bug reports to Intel. John.