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

Structured documentation of relaxed visibility #135

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 2 comments
Open

Structured documentation of relaxed visibility #135

GoogleCodeExporter opened this issue Mar 13, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Per http://code.google.com/p/google-gin/issues/detail?id=86, often classes are 
made public for sake of being accessible by a Ginjector in another package.

It's useful to include an annotation to describe this versus using free form 
comments of the sort:
 // class is public because ....

Annotation file is attached.

Original issue reported on code.google.com by [email protected] on 29 Jan 2011 at 4:15

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant