-
Notifications
You must be signed in to change notification settings - Fork 319
A bit of clean-up in TagMap #10164
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
Open
dougqh
wants to merge
5
commits into
master
Choose a base branch
from
dougqh/tagmap-cleanup
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
A bit of clean-up in TagMap #10164
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
95f5808
A bit of clean-up
dougqh 79092b0
spotless
dougqh 13ad995
Merge branch 'master' into dougqh/tagmap-cleanup
dougqh 8026a5f
Merge branch 'master' into dougqh/tagmap-cleanup
dougqh 854633b
Merge branch 'master' into dougqh/tagmap-cleanup
dougqh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fields declared on an interface are already implicitly static final so IMHO this is redundant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I know, but I prefer to be explicit.
I want to see final, so that I know it is obviously correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally think that we should omit that since it does not improve the readability. A lot of other projects are explicitly suggesting not to do it (i.e. openjdk -> https://cr.openjdk.org/~alundblad/styleguide/index-v6.html).
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least for final, I think it is good to be explicit. Especially given that we have a lot of contributors that aren't regularly working in Java, so including static final sets an example that works in both classes & interfaces.