We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
N4750 26.3.11.2 [vector.cons]/1 defines:
explicit vector(const Allocator&);
But 26.3.11.1 [vector.overview] declared:
explicit vector(const Allocator&) noexcept;
The text was updated successfully, but these errors were encountered:
I thought that only move constructors need noexcept...
Sorry, something went wrong.
This change added noexcept in the synopsis:
commit 6e3b46f Author: Richard Smith richard@metafoo.co.uk Date: Mon Nov 10 17:23:30 2014 -0800
N4258 Cleaning‐up noexcept in the Library [unord.set.overview], [unord.multiset.overview]: Replace meaningless "Container_move_assign" with the intended "Pred".
N4258 Cleaning‐up noexcept in the Library
[unord.set.overview], [unord.multiset.overview]: Replace meaningless "Container_move_assign" with the intended "Pred".
I believe the intent of that paper was clear: make the named std::vector constructor noexcept, so fixing this seems editorial to me.
(I notice that the partial specialization for vector<bool, Allocator> does not have the various noexcept fixes in the constructors.)
vector<bool, Allocator>
noexcept
jensmaurer
Successfully merging a pull request may close this issue.
N4750 26.3.11.2 [vector.cons]/1 defines:
explicit vector(const Allocator&);
But 26.3.11.1 [vector.overview] declared:
explicit vector(const Allocator&) noexcept;
The text was updated successfully, but these errors were encountered: