auto newvar1 = myvector;
// vs:
auto *newvar2 = myvector;
Both of these are the same and will declare a pointer to std::vector<MyClass>
(pointing to random location, since myvector
is uninitialized in your example and likely contains garbage). So basically you can use any one of them. I would prefer auto var = getVector()
, but you may go for auto* var = getVector()
if you think it stresses the intent (that var
is a pointer) better.
I must say I never dreamt of similar uncertainity using auto
. I thought people would just use auto
and not think about it, which is correct 99 % of the time - the need to decorate auto
with something only comes with references and cv-qualifiers.
However, there is slight difference between the two when modifies slightly:
auto newvar1 = myvector, newvar2 = something;
In this case, newvar2
will be a pointer (and something must be too).
auto *newvar1 = myvector, newvar2 = something;
Here, newvar2
is the pointee type, eg. std::vector<MyClass>
, and the initializer must be adequate.
In general, if the initializer is not a braced initializer list, the compiler processes auto
like this:
It produces an artificial function template declaration with one argument of the exact form of the declarator, with auto
replaced by the template parameter. So for auto* x = ...
, it uses
template <class T> void foo(T*);
It tries to resolve the call foo(initializer)
, and looks what gets deduced for T
. This gets substituted back in place of auto
.
If there are more declarators in a single declarations, this is done for all of them. The deduced T
must be the same for all of them...
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…