This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/16915] unnecessary copy construction
- From: "boris at kolpackov dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Aug 2004 15:37:57 -0000
- Subject: [Bug c++/16915] unnecessary copy construction
- References: <20040807183433.16915.boris@kolpackov.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From boris at kolpackov dot net 2004-08-27 15:37 -------
Didn't quite get what is invalid. Is it invalid to use lock_base copy-ctor
instead of lock_<mutex> -or- the code is invalid because lock_base copy-ctor
should be used. If the former then I am glad we finally agree. If the latter
then what about the example from the standard, is it invalid too? I don't see
any semantical differences between "extern B f ()" and "operator lock_<mutex>
()" - they both return rvalue.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16915