Thread: Visual C++ too lenient

I checked in two mistakes that were immediately seen by a guy running clang. I developed this under VS 2013. I would have though MS had fixed this improper leniency by now:

Example 1:

Code:

template <typename X>
class Foo
{
public:
    template <typename X> // I shadowed the outer template parameter and yet it compiles
    class Bar
    {
    };
};

Example 2:

Code:

template <typename X>
class Foo
{
public:
    template <typename T>
    void Bar();
};

Foo<int> x;
x.Bar<int>(); // I need to write x.template Bar<int>() instead, and yet it compiles

ARGH!

The first is obvious and does not compile on GCC as far as I remember, but I'm not sure about the second. I don't have currently access to the standard (nor to compiler) so I won't check, but I would argue that you don't need "template" there, because Foo<int> is fully known to the compiler. "template" keyword for methods is necessary in such scenarios as in DoSomethingWithFoo:

Code:

template <typename X>
class Foo
{
public:

    template <typename Y>
    void Bar();
};

template <typename X>
void DoSomethingWithFoo(Foo<X>& x)
{
    x.template Bar<int>(); // Type of x is unknown - "Bar" is a dependant name.
}

Foo<int> x;
x.Bar<int>(); // Type of x is known.

You're right.. the actual line of code is like this:

Code:

return Foo<A>().template B<C, D>();