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
8188055: (ref) Add Reference::refersTo predicate #498
Closed
Closed
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
4226ae7
new function
kimbarrett 0ddc48f
remove CMS comment
kimbarrett 2bcf123
expand test
kimbarrett 1773052
change referent access
kimbarrett 00b1b90
basic functional test
kimbarrett 28f2d1b
improve refersTo0 descriptions
kimbarrett eb9dfa1
use Object instead of TestObject
kimbarrett 8b7c333
cleanup nits from Mandy
kimbarrett efa40d7
simplify test
kimbarrett c1062ec
More explicit refersTo0 comment.
kimbarrett ab4e519
Merge branch 'master' into refersto
kimbarrett 3a15b6a
improve wording in refersTo javadoc
kimbarrett 79277ff
Merge branch 'master' into refersto
kimbarrett File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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.
It looks to me like the
expectNotCleared()
andexpectNotValue()
methods can be removed. All expect-tests can be done with justexpectCleared()
andexpectValue()
.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 don't think so. For example,
expectNotCleared(testWeak1, "testWeak1")
is not testing the same thing as
expectValue(testWeak1, testObject1, "testWeak1")
If the implementation is correct they will indeed always be consistent. But they could be different with an incorrect implementation.
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.
Doesn't that just depend on how you implement
expectValue()
/expectCleared()
? You could for example implementexpectValue()
/expectCleared()
to be supersets ofexpectNotCleared()
/expectNotValue()
, which I think would make this easier to read. Something like this: