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 such a clear win.
It has its costs. It will increase generated code size which will lead to a
larger binary. For some Google binaries where protos contribute to half of
the binary size, the size increase might be significant. More generated
code also means longer compilation time. For the benefit of move
constructors, we have already done some experiments which show no sign of
performance improvements after adding move constructors. It's probably
because our existing code is already highly optimized to avoid unnecessary
copies. It's hard to find a piece of performance crucial code that can be
improved with move constructors. To decide whether to add move
constructors, the authority wants to see: data showing the impact of the
generated code size change, and examples showing how the new API can
improve the clarity of our existing code. I guess there is not much a
non-googler could help here.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups "Protocol
Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
