public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/9626: g++ accepts vector<vector<int> > v(2, 4); Date: Sat, 08 Feb 2003 13:56:00 -0000 [thread overview] Message-ID: <20030208135600.6032.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/9626; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: paolo@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, paolo@gcc.gnu.org Subject: Re: libstdc++/9626: g++ accepts vector<vector<int> > v(2, 4); Date: 08 Feb 2003 14:48:07 +0100 paolo@gcc.gnu.org writes: > Synopsis: g++ accepts vector<vector<int> > v(2, 4); > > State-Changed-From-To: analyzed->feedback > State-Changed-By: paolo > State-Changed-When: Sat Feb 8 13:36:01 2003 > State-Changed-Why: > On second thought, doesn't seem to me that your testcase is > illegal. You are asking for a size 2 vector of size 4 vectors: > there are no implicit conversions which should be prevented by > explicit, since 4 is the argument of the explicit vector(const > A& = A()) constructor of each of them and this seems perfectly > legal. Agreed? No. I pass a 4, but the constructor expects an A = vector<int>. The only way to make a "vector<int>" from "4" is with an "explicit" constructor. -- Falk
next reply other threads:[~2003-02-08 13:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-08 13:56 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-08 15:36 Paolo Carlini 2003-02-08 15:26 Falk Hueffner 2003-02-08 15:25 paolo 2003-02-08 13:56 Paolo Carlini 2003-02-08 13:46 Paolo Carlini 2003-02-08 13:36 paolo 2003-02-08 9:25 paolo
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=20030208135600.6032.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=paolo@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).