What's the difference between `auto x = vector()` and `vector x`?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am writing some code and have a question.
What is the difference between auto x = vector<int>();
and vector<int> x;
? Are they all the same or there's some difference with the complexity?
c++ vector stl initialization
add a comment |
I am writing some code and have a question.
What is the difference between auto x = vector<int>();
and vector<int> x;
? Are they all the same or there's some difference with the complexity?
c++ vector stl initialization
2
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago
add a comment |
I am writing some code and have a question.
What is the difference between auto x = vector<int>();
and vector<int> x;
? Are they all the same or there's some difference with the complexity?
c++ vector stl initialization
I am writing some code and have a question.
What is the difference between auto x = vector<int>();
and vector<int> x;
? Are they all the same or there's some difference with the complexity?
c++ vector stl initialization
c++ vector stl initialization
edited 1 hour ago
songyuanyao
94.5k11182250
94.5k11182250
asked 1 hour ago
AutoratchAutoratch
555
555
2
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago
add a comment |
2
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago
2
2
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
They have the same effect since C++17. Both construct an object named x
with type std::vector<int>
, which is initialized by the default constructor of std::vector
.
Precisely the 1st one is copy initialization, x
is copy-initialized from a value-initialized temporary. From C++17 this kind of copy elision is guaranteed, as the result x
is initialized by the default constructor of std::vector
directly. Before C++17, copy elision is an optimization:
even when it takes place and the copy/move (since C++11) constructor is not called, it still must be present and accessible (as if no optimization happened at all), otherwise the program is ill-formed:
The 2nd one is default initialization, as a class type x
is initialized by the default constructor of std::vector
.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55700049%2fwhats-the-difference-between-auto-x-vectorint-and-vectorint-x%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
They have the same effect since C++17. Both construct an object named x
with type std::vector<int>
, which is initialized by the default constructor of std::vector
.
Precisely the 1st one is copy initialization, x
is copy-initialized from a value-initialized temporary. From C++17 this kind of copy elision is guaranteed, as the result x
is initialized by the default constructor of std::vector
directly. Before C++17, copy elision is an optimization:
even when it takes place and the copy/move (since C++11) constructor is not called, it still must be present and accessible (as if no optimization happened at all), otherwise the program is ill-formed:
The 2nd one is default initialization, as a class type x
is initialized by the default constructor of std::vector
.
add a comment |
They have the same effect since C++17. Both construct an object named x
with type std::vector<int>
, which is initialized by the default constructor of std::vector
.
Precisely the 1st one is copy initialization, x
is copy-initialized from a value-initialized temporary. From C++17 this kind of copy elision is guaranteed, as the result x
is initialized by the default constructor of std::vector
directly. Before C++17, copy elision is an optimization:
even when it takes place and the copy/move (since C++11) constructor is not called, it still must be present and accessible (as if no optimization happened at all), otherwise the program is ill-formed:
The 2nd one is default initialization, as a class type x
is initialized by the default constructor of std::vector
.
add a comment |
They have the same effect since C++17. Both construct an object named x
with type std::vector<int>
, which is initialized by the default constructor of std::vector
.
Precisely the 1st one is copy initialization, x
is copy-initialized from a value-initialized temporary. From C++17 this kind of copy elision is guaranteed, as the result x
is initialized by the default constructor of std::vector
directly. Before C++17, copy elision is an optimization:
even when it takes place and the copy/move (since C++11) constructor is not called, it still must be present and accessible (as if no optimization happened at all), otherwise the program is ill-formed:
The 2nd one is default initialization, as a class type x
is initialized by the default constructor of std::vector
.
They have the same effect since C++17. Both construct an object named x
with type std::vector<int>
, which is initialized by the default constructor of std::vector
.
Precisely the 1st one is copy initialization, x
is copy-initialized from a value-initialized temporary. From C++17 this kind of copy elision is guaranteed, as the result x
is initialized by the default constructor of std::vector
directly. Before C++17, copy elision is an optimization:
even when it takes place and the copy/move (since C++11) constructor is not called, it still must be present and accessible (as if no optimization happened at all), otherwise the program is ill-formed:
The 2nd one is default initialization, as a class type x
is initialized by the default constructor of std::vector
.
edited 1 hour ago
answered 1 hour ago
songyuanyaosongyuanyao
94.5k11182250
94.5k11182250
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55700049%2fwhats-the-difference-between-auto-x-vectorint-and-vectorint-x%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
The first results in a call to a default constructor and a call to a move constructor. The second results in a call to a default constructor. Even if the compiler optimizes both to result in the same assembly, the second one is the one to go for readability.
– DeiDei
1 hour ago