public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "darkdragon-001 at web dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/63753] New: std::transform does not change size Date: Wed, 05 Nov 2014 18:29:00 -0000 [thread overview] Message-ID: <bug-63753-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63753 Bug ID: 63753 Summary: std::transform does not change size Product: gcc Version: 4.9.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: darkdragon-001 at web dot de When using std::transform with a OutputIterator to std::vector then the vector size is not updated (see code attached): #include <algorithm> #include <iostream> #include <vector> using namespace std; int main() { vector<double> v = {1,2,3,4,5}; vector<double> r; r.reserve(v.size()); transform(v.begin(),v.end(),r.begin(),[](const double& d) { return 2*d; }); cout << "size:" << r.size() << "front:" << r.front() << endl; return 0; }
next reply other threads:[~2014-11-05 18:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-05 18:29 darkdragon-001 at web dot de [this message] 2014-11-05 22:15 ` [Bug libstdc++/63753] " glisse at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-63753-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).