Fix JarInfer parameter indexes for instance methods #1071
Merged
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.
Previously, when JarInfer wrote an
astubx
file, it treated the receiver parameter of an instance method as being at parameter index 0. In other places we do library modeling, the receiver parameter is ignored and the next parameter is treated as being at index 0. The latter handling is more sensible for NullAway, as we have not needed to do any kind of library modeling of receiver parameters yet.This PR switches the JarInfer logic to ignore the receiver parameter like in other places. This breaks pre-existing
astubx
files, so we disable an integration test for now. We will bump the astubx version and fix up existing files in a later PR as part of an overall fix to #1072 (fixing in multiple PRs to ease reviewing).