-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove RepeatedField
#503
Comments
This gives a little speedup when reusing existing messages to read in loop, like this:
Maybe it is overengineering and not really needed, but it would be hard to remove |
Hmm just to make sure I'm understanding correctly, do you mean that I totally agree without it being hard to remove |
Basically, this operation is done without allocations:
That said, this feature is used very infrequently, and This changes won't be backported to version 3 (because of backwards compatibility), instead, version 3 will be released soon. |
Great, thank you! |
Maybe rust-protobuf 3 need an option to generate |
The documentation of
RepeatedField
claims that it is aHowever, the documentation of
Vec::clear
states thatWhich means that
Vec::clear
already does not deallocate.As such, I think it'd make sense to just remove
RepeatedField
altogether, for version 3.Related issue: #84
The text was updated successfully, but these errors were encountered: