Why doesn’t the C++11 ‘auto’ keyword work for static members?

by

It’s disallowed by the language:

[C++11: 7.1.6.4]:

1 The auto type-specifier signifies that the type of a variable being declared shall be deduced from its initializer or that a function declarator shall include a trailing-return-type.

2 The auto type-specifier may appear with a function declarator with a trailing-return-type (8.3.5) in any context where such a declarator is valid.

3 Otherwise, the type of the variable is deduced from its initializer. The name of the variable being declared shall not appear in the initializer expression. This use of auto is allowed when declaring variables in a block (6.3), in namespace scope (3.3.6), and in a for-init-statement (6.5.3). auto shall appear as one of the decl-specifiers in the decl-specifier-seq and the decl-specifier-seq shall be followed by one or more init-declarators, each of which shall have a non-empty initializer.

4 The auto type-specifier can also be used in declaring a variable in the condition of a selection statement (6.4) or an iteration statement (6.5), in the type-specifier-seq in the new-type-id or type-id of a new-expression (5.3.4), in a for-range-declaration, and in declaring a static data member with a brace-or-equal-initializer that appears within the member-specification of a class definition (9.4.2).

5 A program that uses auto in a context not explicitly allowed in this section is ill-formed.

It’s hard to prove a negative, but there’s simply no explicit rule in the standard to allow auto in your case.

However, the same rules mean that the following is valid:

struct Foo {
   static constexpr auto constant_string = "foo";
};

int main() {}

(Note that the type of Foo::constant_string is char const* const rather than, say, char const[3]; this is an effect of using auto.)

More Related Contents:

  1. Why can I use auto on a private type?
  2. How much is too much with C++11 auto keyword?
  3. What is the type of lambda when deduced with “auto” in C++11?
  4. Should the trailing return type syntax style become the default for new C++11 programs? [closed]
  5. What does auto&& tell us?
  6. Arrow operator (->) in function heading
  7. Why does auto x{3} deduce an initializer_list?
  8. Range-for-loops and std::vector
  9. C++ auto keyword. Why is it magic?
  10. C++11 auto: what if it gets a constant reference?
  11. Can the use of C++11’s ‘auto’ improve performance?
  12. C++11 – declaring non-static data members as ‘auto’
  13. The new keyword “auto”; When should it be used to declare a variable type? [duplicate]
  14. Advantage of using trailing return type in C++11 functions
  15. C++11 Change `auto` Lambda to a different Lambda?
  16. Does ‘auto’ type assignments of a pointer in c++11 require ‘*’?
  17. “does not name a type” error c++ [duplicate]
  18. Why can I not push_back a unique_ptr into a vector?
  19. Are the days of passing const std::string & as a parameter over?
  20. Why would the behavior of std::memcpy be undefined for objects that are not TriviallyCopyable?
  21. Isn’t the template argument (the signature) of std::function part of its type?
  22. Volatile in C++11
  23. Do I really need to implement user-provided constructor for const objects?
  24. Is it valid to bind non-const lvalue-references to rvalues in C++ 11?(modified)
  25. What’s the difference between parentheses and braces in c++ when constructing objects
  26. cc1plus: error: unrecognized command line option “-std=c++11” with g++
  27. How do I pass multiple ints into a vector at once?
  28. Is it wise to ignore gcc/clang’s “-Wmissing-braces” warning?
  29. Can std::vector emplace_back copy construct from an element of the vector itself?
  30. stl random distributions and portability

Leave a Comment