Hi,
I just created a repository trying to add C++11 features to ProtoBuf.
Move constructor is a really good feature to be included. As I just joined
the group and looks like I can't get the patch you posted, do you mind
share it again?
Thanks!
On Monday, May 5, 2014 at 3:47:01 AM UTC+10,
Comment #17 on issue 447 by xiaof...@google.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Feel free to create a github issue for this as we don't have a plan for
automated migration of issues.
From our point of view, adding move constructors is not
Comment #16 on issue 447 by benjamin...@gmail.com: No C++11 move
constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Now that protobuf is hosted on github: https://github.com/google/protobuf
Should we manually move this ticket to a github issue? Or is there a plan
to do
Comment #15 on issue 447 by t...@ripple.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
This *is* unfortunate.
In particular, whomever the gatekeeper is for this isn't actually telling
us why they aren't convinced - so how can we respond? It seems
Comment #14 on issue 447 by mend...@gmail.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
So a move constructor (eventually marked as noexcept) is not a peformance
gain? Right!
--
You received this message because this project is configured to send
Updates:
Status: WontFix
Owner: xiaof...@google.com
Comment #10 on issue 447 by xiaof...@google.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
FYI.
Google's Style Guide now permits rvalue references to be used in move
constructors and
Comment #11 on issue 447 by chen3feng: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Very disappointed to hear this message.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust
Comment #12 on issue 447 by cbsm...@gmail.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Speaks volumes that after 22 months after submission and 5 months after a
working plugin was contributed, there isn't even a direct answer.
--
You received this
Comment #13 on issue 447 by chen3feng: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
let't make a fork on github?
2014-10-16 上午11:01于 proto...@googlecode.com写道：
--
You received this message because this project is configured to send all
issue
Comment #9 on issue 447 by arnethed...@gmail.com: No C++11 move constructors
http://code.google.com/p/protobuf/issues/detail?id=447
Attaching a compiler plugin which adds move construction, assignment and
string move assignment to the generated C++ code - to use, simply add
Comment #8 on issue 447 by m...@google.com: No C++11 move constructors
http://code.google.com/p/protobuf/issues/detail?id=447
Any updates on this?
Attached is a patch is that adds a move constructor and assignment operator
to the generated messages.
Attachments:
patch 2.4 KB
--
Comment #7 on issue 447 by danielw...@google.com: No C++11 move constructors
http://code.google.com/p/protobuf/issues/detail?id=447
Looks like the internal style guide now permits rvalue references. This
isn't reflected in the externally published style guide, but I'm guessing
that's a
Comment #3 on issue 447 by mike.naq...@gmail.com: No C++11 move constructors
http://code.google.com/p/protobuf/issues/detail?id=447
I think there are some simple C++11 #ifdefs to address this for GCC/Clang
and VS, so it should be doable. This would be a huge win in performance in
same
Comment #2 on issue 447 by jacek.si...@grasshopperasia.com: No C++11 move
constructors
http://code.google.com/p/protobuf/issues/detail?id=447
An option to protoc or the preprocessor could solve backward compatibility
--
You received this message because you are subscribed to the Google
14 matches
Mail list logo
