Avoid exposing some types outside the scope in which those types are visible. #6777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid exposing some types outside the scope in which those types are visible.
Java doesn't mind this, but it's not like it's accomplishing anything for us.
I've tried to make things
private
where possible and fallen back to making types package-private where necessary.(In
Synchronized
, I made everything package-private for consistency, rather than trying to trace through the class hierarchies to expose only the types that need it.)I also sprinkled in some
final
keywords while I was in the area.RELNOTES=n/a