trailing-return-type and point of declaration
6.3.2 [basic.scope.pdecl]
Jason Merrill

Created on 2011-12-20.00:00:00 last changed 101 months ago


Date: 2012-02-15.00:00:00

Rationale (February, 2012):

This is a request for an extension to the language and is thus more appropriately addressed by EWG.

Date: 2011-12-20.00:00:00

This seems like it should be well-formed:

    template <class T> T list(T x);

    template <class H, class ...T>
    auto list(H h, T ...args) -> decltype(list(args...));

    auto list3 = list(1, 2, 3);

but it isn't, because the second list isn't in scope in its own trailing-return-type; the point of declaration is after the declarator, which includes the trailing-return-type. And since int has no associated namespaces, the call in the return type only sees the first list. G++, EDG and Clang all reject the testcase on this basis.

But this seems like a natural pattern for writing variadic function templates, and we could support it by moving the point of declaration to the ->. This would mean having to deal with a function that only has a placeholder for a return type, but I think we can handle that.

Date User Action Args
2012-02-27 00:00:00adminsetmessages: + msg3861
2012-02-27 00:00:00adminsetstatus: open -> extension
2011-12-20 00:00:00admincreate