Skip to content
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

public class ExtensionRegistry becomes non-final in 2.6.0; by design? #22

Closed
protobufel opened this issue Sep 15, 2014 · 2 comments
Closed

Comments

@protobufel
Copy link

Is it a bug, or a feature?

David

@liujisi
Copy link
Contributor

liujisi commented Sep 15, 2014

Internally we have a subclass in the same package which is not opensourced. The ExtensionRegistry is not intended to be sub-classed by the users though.

@protobufel
Copy link
Author

I think it's a potential security risk; version 2.5.0 had this class final. Just raising question, if it is an oversight.

@liujisi liujisi closed this as completed Mar 5, 2015
TeBoring pushed a commit to TeBoring/protobuf that referenced this issue Jan 19, 2019
Generating enums and intentries only if the tables are non-empty.
GerHobbelt pushed a commit to GerHobbelt/protobuf that referenced this issue Aug 4, 2024
yordis pushed a commit to yordis/protobuf that referenced this issue Dec 8, 2024
Use macro to centralize wire types declaration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants